菜单
Create, patch, lint, discover, trace, and complete docs-first specs. Use when working in Codex and the user needs tx commands from this area.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | tx-docs-specs |
| description | Create, patch, lint, discover, trace, and complete docs-first specs. Use when working in Codex and the user needs tx commands from this area. |
| metadata | {"short-description":"Create, patch, lint, discover, trace, and complete docs-first specs."} |
Use when the user is working in PRDs, DDs, invariants, decision tracking, or markdown export flows.
tx doc add prd <name> --title "Title"tx spec discovertx spec statustx decision: Manage decisions as first-class artifactstx decompose: Create a task graph from a design spectx doc: Manage docs-as-primitivestx doc add: Create a new doctx doc attach: Attach a doc to a tasktx doc edit: Open doc YAML in editortx doc link: Link two docstx doc list: List all docstx doc lock: Lock a doc versiontx doc patch: Create a design patch doctx doc rm: Remove latest mutable doc versiontx doc rm: Remove latest mutable doc versiontx doc show: Show doc detailstx doc sync: Re-read docs from disk and update DB hashestx doc validate: Validate doc/task coverage and index search metadatatx doc version: Create new version from locked doctx invariant is deprecated. Use 'tx spec' instead.tx md-export: Export tasks to markdown filetx spec: Docs-first spec-to-test traceability primitivestx spec batch: Import test run results from stdintx spec complete: Record human completion sign-offtx spec discover: Refresh doc-derived invariants and upsert test mappingstx spec fci: Compute Feature Completion Indextx spec gaps: List uncovered invariants (no linked tests)tx spec health: Repo-level spec-driven development rolluptx spec link: Manually link an invariant to a testtx spec lint: All-in-one spec and doc checkertx spec matrix: Full invariant-to-test traceability matrixtx spec run: Record a pass/fail run result for a canonical test IDtx spec status: Explain scope closure statetx spec tests: List tests linked to an invarianttx spec unlink: Remove an invariant/test mappingtx triangle is a deprecated alias for 'tx spec health'.Read references/commands.md for the full generated CLI help text for this skill's commands.
When working in Codex, prefer rg -n <pattern> <path> and rg --files <path> over broad grep -r or fragile find pipelines.
If a shell/search command fails because of malformed flags, truncated paths, or broken quotes:
rg command with an explicit directorynode_modul or unterminated quotesgrep -r with rg -n unless rg is unavailablefind probes with rg --files when you are really locating source files