tx

Turn a design spec into an explicit tx task graph with `tx decompose`, then refine the graph using normal tx task and dependency primitives.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Create, patch, lint, discover, trace, and complete docs-first specs. Use when working in Codex and the user needs tx commands from this area.

Guide for working with tx task management. Use when picking up tasks, completing work, or managing dependencies.

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.

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.

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.

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%.

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.

Refresh bundled tx Claude Code and Codex skills in a project from the canonical tx source without manual copy and paste.

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.

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.

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.

Model blockers, parent-child relationships, and shared group context. Use when working in Claude Code and the user needs tx commands from this area.

Inspect graph anchors plus supporting utility and usage commands. Use when working in Claude Code and the user needs tx commands from this area.

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.

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.

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.

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.

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.

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.

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.

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%.

Configure gates, guards, labels, verification, and retrospectives for bounded autonomy. Use when working in Codex and the user needs tx commands from this area.

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.

Model blockers, parent-child relationships, and shared group context. Use when working in Codex and the user needs tx commands from this area.

Inspect graph anchors plus supporting utility and usage commands. Use when working in Codex and the user needs tx commands from this area.

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.

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.

Inspect queue health, diagnostics, dashboards, run traces, and recent failures. Use when working in Codex and the user needs tx commands from this area.

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.