원클릭으로
tx-workflow
Guide for working with tx task management. Use when picking up tasks, completing work, or managing dependencies.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Guide for working with tx task management. Use when picking up tasks, completing work, or managing dependencies.
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-workflow |
| description | Guide for working with tx task management. Use when picking up tasks, completing work, or managing dependencies. |
tx ready --limit 1 --json to get the next unblocked tasktx show <id> to see full details, dependencies, and contexttx memory context <id> to get relevant learnings for the tasktx showtx memory context <id> or tx memory recall <file-path>tx group-context set <id> "<shared context>"ears_requirements and validate with tx doc lint-ears <doc-name-or-yaml-path>tx memory add "what you discovered"bunx --bun vitest run <paths>)tx done <id> to mark the task completetx ready to see if new tasks became availableIf a task is too large, break it down:
tx add "Sub-task title" --parent <parent-id> --description "Details"
# Task B can't start until Task A is done
tx dep block <task-B-id> <task-A-id>
# Remove a dependency
tx dep unblock <task-B-id> <task-A-id>
# General learning
tx memory add "Effect.try catch handler puts errors in the error channel, not success"
# File-specific learning
tx memory learn "src/auth/*.ts" "Auth tokens expire after 24h, refresh logic is in token-service.ts"
# Recall learnings for a file
tx memory recall src/auth/token-service.ts