| name | tx-workflow |
| description | Guide for working with tx task management. Use when picking up tasks, completing work, or managing dependencies. |
tx Workflow
Picking Up a Task
- Run
tx ready --limit 1 --json to get the next unblocked task
- Run
tx show <id> to see full details, dependencies, and context
- Run
tx memory context <id> to get relevant learnings for the task
Working on a Task
- Understand the task requirements from
tx show
- Check for relevant learnings with
tx memory context <id> or tx memory recall <file-path>
- If related tasks share context, set it once with
tx group-context set <id> "<shared context>"
- If PRD docs are in scope, prefer
ears_requirements and validate with tx doc lint-ears <doc-name-or-yaml-path>
- Implement the changes
- Add or update integration tests for critical flows (happy path + failure path)
- If telemetry code changed, verify OTEL remains non-blocking (noop/configured/exporter-failure paths)
- Record anything you learned:
tx memory add "what you discovered"
Completing a Task
- Run targeted tests for changed files before completion (
bunx --bun vitest run <paths>)
- Run
tx done <id> to mark the task complete
- This automatically unblocks any tasks that depended on this one
- Check
tx ready to see if new tasks became available
Creating Sub-tasks
If a task is too large, break it down:
tx add "Sub-task title" --parent <parent-id> --description "Details"
Managing Dependencies
tx dep block <task-B-id> <task-A-id>
tx dep unblock <task-B-id> <task-A-id>
Recording Learnings
tx memory add "Effect.try catch handler puts errors in the error channel, not success"
tx memory learn "src/auth/*.ts" "Auth tokens expire after 24h, refresh logic is in token-service.ts"
tx memory recall src/auth/token-service.ts