メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | tx-core-loop |
| description | 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. |
| metadata | {"short-description":"Work the main tx queue: initialize, create tasks, inspect work, claim tasks, and complete them."} |
Use when the user is setting up tx or moving normal task work through the queue.
tx ready --limit 1 --jsontx show <task-id>tx done <task-id>tx add: Create a new tasktx bulk: Batch operations on multiple taskstx claim: Claim a task for a worker with a leasetx claim release: Release a claim on a tasktx claim renew: Renew the lease on a claimtx delete: Delete a tasktx done: Mark task completetx help: Show helptx init: Initialize task databasetx list: List taskstx ready: List ready taskstx reset: Reset task to ready statustx show: Show task detailstx update: Update a taskRead 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 filesTurn 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.