jamesaphoenix
63 verified skills126 total stars
docs-diagrams
Add or refine diagrams in documentation, especially Mermaid workflow diagrams in apps/docs. Use when a docs page explains actor handoffs, phase gates, failure paths, state transitions, or multi-step flows that are clearer as a diagram.
testing2
ralph-loop
Run Ralph against either the full repo queue or tasks linked to one design doc, with injected task/spec/queue context for Codex or Claude runtimes.
development2
release
Release a new lockstep version of tx to GitHub and npm with preflight validation, workflow monitoring, and registry verification.
tools2
skills-sync
Refresh bundled tx Claude Code and Codex skills in a project from the canonical tx source without manual copy and paste.
development2
surface-parity
Internal closed-loop skill: drive CLI/API/MCP to 100% shape parity (same service methods) AND behaviour parity (same response shapes). Uses ESLint rules tx/require-surface-parity + tx/interface-parity. NOT shipped to tx users.
tools2
system-design-doc
Generate a system-level design document via `tx doc add design`. Covers cross-cutting architecture, service boundaries, data flows, scalability, and deployment topology. References plan via file path instead of embedding. Plan lives in ~/.claude/plans/<name>.md. Use for system-wide or multi-domain designs rather than feature-scoped subsystem docs.
devops2
tx-autonomy-controls
Configure gates, guards, labels, verification, and retrospectives for bounded autonomy. Use when working in Claude Code and the user needs tx commands from this area.
development2
test-diagnostics
Profile all test files to find slow, hanging, or failing tests. Use when tests seem slow or when vitest hangs.
testing2
tx-graph-utils
Inspect graph anchors plus supporting utility and usage commands. Use when working in Claude Code and the user needs tx commands from this area.
tools2
tx-workers-runtime
Operate workers, daemons, coordinators, cycle scans, and hook installation paths. Use when working in Claude Code and the user needs tx commands from this area.
development2
verify-invariants
Implement and verify design doc invariants by annotating tests and source code with [INV-*] / @spec tags, then driving tx spec coverage from BUILD toward HARDEN (100% FCI). Works with any design doc that has an invariants block.
development2
tx-sync-data
Export, import, migrate, hydrate, and compact task state and sync artifacts. Use when working in Claude Code and the user needs tx commands from this area.
development2
docs-diagrams
Add or refine diagrams in documentation, especially Mermaid workflow diagrams in apps/docs. Use when a docs page explains actor handoffs, phase gates, failure paths, state transitions, or multi-step flows that are clearer as a diagram.
testing2
design-doc
Generate a detailed design document via `tx doc add design`. Covers architecture, interfaces, data model, invariants, failure modes, verification, and testing strategy. References plan via file path instead of embedding. Plan lives in ~/.codex/plans/<name>.md. Reads companion PRD automatically to map EARS requirements to invariants. Output lands in specs/design/<name>.md.
development2
skills-sync
Refresh bundled tx Claude Code and Codex skills in a project from the canonical tx source without manual copy and paste.
development2
release
Cut a lockstep tx release with enforced preflight validation, workflow monitoring, and npm verification. Use when bumping versions, tagging releases, repairing partial publishes, or checking publish readiness.
testing2
surface-parity
Internal closed-loop skill: drive CLI/API/MCP to 100% shape parity (same service methods) AND behaviour parity (same response shapes). Uses ESLint rules tx/require-surface-parity + tx/interface-parity. NOT shipped to tx users.
tools2
tx-core-loop
Work the main tx queue: initialize, create tasks, inspect work, claim tasks, and complete them. Use when working in Codex and the user needs tx commands from this area.
development2
tx-autonomy-controls
Configure gates, guards, labels, verification, and retrospectives for bounded autonomy. Use when working in Codex and the user needs tx commands from this area.
development2
tx-memory-context
Store, recall, search, and relate memory documents, learnings, and task context. Use when working in Codex and the user needs tx commands from this area.
development2
tx-messaging-pins
Send agent messages, acknowledge inbox items, and persist shared context pins. Use when working in Codex and the user needs tx commands from this area.
development2
tx-observability-traces
Inspect queue health, diagnostics, dashboards, run traces, and recent failures. Use when working in Codex and the user needs tx commands from this area.
development2
tx-sync-data
Export, import, migrate, hydrate, and compact task state and sync artifacts. Use when working in Codex and the user needs tx commands from this area.
development2
tx-workers-runtime
Operate workers, daemons, coordinators, cycle scans, and hook installation paths. Use when working in Codex and the user needs tx commands from this area.
development2
tx-workflow
Guide for working with tx task management. Use when picking up tasks, completing work, or managing dependencies.
testing2
verify-build
Build a verification script that defines "done" for a parent task or project phase. Creates a .sh script and attaches it via tx auto verify set.
development2
verify-invariants
Implement and verify design doc invariants by annotating tests and source code with [INV-*] / @spec tags, then driving tx spec coverage from BUILD toward HARDEN (100% FCI). Works with any design doc that has an invariants block.
development2
map-invariants
Auto-annotate existing tests and source code with [INV-*] / @spec tags by reading all spec gaps, understanding each invariant, and matching them to existing test assertions. Optionally creates missing tests too. Drives FCI from 0% toward 100%.
development2
ralph-loop
Run Ralph against either the full repo queue or tasks linked to one design doc, with injected task/spec/queue context for Codex or Claude runtimes.
development2
task-spec-loop
Link tasks to paired PRD/design specs, export all open work to markdown, and keep Ralph-style loops moving by creating tasks, subtasks, and dependency updates through tx primitives.
data-ai2
decompose-spec
Turn a design spec into an explicit tx task graph with `tx decompose`, then refine the graph using normal tx task and dependency primitives.
testing2
skills-sync
Refresh bundled tx Claude Code and Codex skills in a project from the canonical tx source without manual copy and paste.
development2
test-quiet
Run tests with context-efficient output. Hides passing test output, shows ONLY failures. Use when running tests, checking if tests pass, or verifying changes. Also detects flaky tests.
testing2
system-design-doc
Generate a system-level design document via `tx doc add design`. Covers cross-cutting architecture, service boundaries, data flows, scalability, and deployment topology. References plan via file path instead of embedding. Plan lives in ~/.codex/plans/<name>.md. Use for system-wide or multi-domain designs rather than feature-scoped subsystem docs.
development2
map-invariants
Auto-annotate existing tests and source code with [INV-*] / @spec tags by reading all spec gaps, understanding each invariant, and matching them to existing test assertions. Optionally creates missing tests too. Drives FCI from 0% toward 100%.
development2
decompose-spec
Turn a design spec into an explicit tx task graph with `tx decompose`, then refine the graph using normal tx task and dependency primitives.
testing2
overview-spec
Generate a system overview spec via `tx doc add overview`. Produces an architectural overview covering problem, scope, components, data flows, and non-goals. References plan via file path instead of embedding. Plan lives in ~/.claude/plans/<name>.md. Output lands in specs/<name>.md with tx-managed frontmatter.
development2
ralph-loop
Run Ralph against either the full repo queue or tasks linked to one design doc, with injected task/spec/queue context for Codex or Claude runtimes.
development2
tx-dependencies-hierarchy
Model blockers, parent-child relationships, and shared group context. Use when working in Codex and the user needs tx commands from this area.
development2
task-spec-loop
Link tasks to paired PRD/design specs, export all open work to markdown, and keep Ralph-style loops moving by creating tasks, subtasks, and dependency updates through tx primitives.
data-ai2
tx-cycle
Run a tx cycle scan — sub-agent swarm for automated codebase issue discovery. Use when the user mentions "cycle", "scan", or "find issues".
development2
tx-docs-specs
Create, patch, lint, discover, trace, and complete docs-first specs. Use when working in Claude Code and the user needs tx commands from this area.
development2
tx-memory-context
Store, recall, search, and relate memory documents, learnings, and task context. Use when working in Claude Code and the user needs tx commands from this area.
development2
tx-graph-utils
Inspect graph anchors plus supporting utility and usage commands. Use when working in Codex and the user needs tx commands from this area.
tools2
verify-build
Build a verification script that defines "done" for a parent task or project phase. Creates a .sh script and attaches it via tx auto verify set.
development2
verify-invariants
Implement and verify design doc invariants by annotating tests and source code with [INV-*] / @spec tags, then driving tx spec coverage from BUILD toward HARDEN (100% FCI). Works with any design doc that has an invariants block.
development2
tx-observability-traces
Inspect queue health, diagnostics, dashboards, run traces, and recent failures. Use when working in Claude Code and the user needs tx commands from this area.
development2
tx-messaging-pins
Send agent messages, acknowledge inbox items, and persist shared context pins. Use when working in Claude Code and the user needs tx commands from this area.
development2
tx-docs-specs
Create, patch, lint, discover, trace, and complete docs-first specs. Use when working in Codex and the user needs tx commands from this area.
development2
tx-dependencies-hierarchy
Model blockers, parent-child relationships, and shared group context. Use when working in Claude Code and the user needs tx commands from this area.
development2
tx-core-loop
Work the main tx queue: initialize, create tasks, inspect work, claim tasks, and complete them. Use when working in Claude Code and the user needs tx commands from this area.
development2
task-spec-loop
Link tasks to paired PRD/design specs, export all open work to markdown, and keep Ralph-style loops moving by creating tasks, subtasks, and dependency updates through tx primitives.
data-ai2
prd
Generate a detailed Product Requirements Document via `tx doc add prd`. Uses EARS requirement syntax with traceable IDs, acceptance criteria, and non-functional requirements. References plan via file path instead of embedding. Plan lives in ~/.claude/plans/<name>.md. Designed to be created alongside a companion `/design-doc`. Output lands in specs/prd/<name>.md.
documentation2
prd
Generate a detailed Product Requirements Document via `tx doc add prd`. Uses EARS requirement syntax with traceable IDs, acceptance criteria, and non-functional requirements. References plan via file path instead of embedding. Plan lives in ~/.codex/plans/<name>.md. Designed to be created alongside a companion `design-doc`. Output lands in specs/prd/<name>.md.
development2
prd
Generate a detailed Product Requirements Document via `tx doc add prd`. Uses EARS requirement syntax with traceable IDs, acceptance criteria, and non-functional requirements. References plan via file path instead of embedding. Plan lives in ~/.claude/plans/<name>.md. Designed to be created alongside a companion `/design-doc`. Output lands in specs/prd/<name>.md.
documentation2
overview-spec
Generate a system overview spec via `tx doc add overview`. Produces an architectural overview covering problem, scope, components, data flows, and non-goals. References plan via file path instead of embedding. Plan lives in ~/.codex/plans/<name>.md. Output lands in specs/<name>.md with tx-managed frontmatter.
development2
overview-spec
Generate a system overview spec via `tx doc add overview`. Produces an architectural overview covering problem, scope, components, data flows, and non-goals. References plan via file path instead of embedding. Plan lives in ~/.claude/plans/<name>.md. Output lands in specs/<name>.md with tx-managed frontmatter.
development2
map-invariants
Auto-annotate existing tests and source code with [INV-*] / @spec tags by reading all spec gaps, understanding each invariant, and matching them to existing test assertions. Optionally creates missing tests too. Drives FCI from 0% toward 100%.
development2
design-doc
Generate a detailed design document via `tx doc add design`. Covers architecture, interfaces, data model, invariants, failure modes, verification, and testing strategy. References plan via file path instead of embedding. Plan lives in ~/.claude/plans/<name>.md. Reads companion PRD automatically to map EARS requirements to invariants. Output lands in specs/design/<name>.md.
testing2
design-doc
Generate a detailed design document via `tx doc add design`. Covers architecture, interfaces, data model, invariants, failure modes, verification, and testing strategy. References plan via file path instead of embedding. Plan lives in ~/.claude/plans/<name>.md. Reads companion PRD automatically to map EARS requirements to invariants. Output lands in specs/design/<name>.md.
testing2
decompose-spec
Turn a design spec into an explicit tx task graph with `tx decompose`, then refine the graph using normal tx task and dependency primitives.
testing2
debug-hooks
Debug Claude Code hook artifacts. Use when investigating why ralph failed, what hooks fired, what was blocked, or reviewing hook behavior for a run.
development2
cycle
Run a tx cycle scan — sub-agent swarm for codebase issue discovery. Use when the user explicitly mentions "cycle". Do NOT use Claude Code teams (TeamCreate/SendMessage) for this — use tx cycle CLI instead.
tools2