Purpose: Step-by-step workflow for JSON-driven task management
Last Updated: 2026-01-11
.tmp/tasks/ (at project root)1. Initiation → TaskManager creates task.json + subtasks
2. Selection → Find eligible tasks (deps satisfied)
3. Execution → Working agent implements task
4. Verification → TaskManager validates completion
5. Archiving → Move to completed/ when done
Create feature folder and files:
.tmp/tasks/{feature-slug}/
├── task.json
├── subtask_01.json
├── subtask_02.json
└── subtask_03.json
Validate with: task-cli.ts validate {feature}
Find eligible tasks using CLI:
task-cli.ts next {feature} # All ready tasks
task-cli.ts parallel {feature} # Parallelizable only
Selection criteria:
status == "pending"depends_on tasks have status == "completed"When picking up task:
json
{
"status": "in_progress",
"agent_id": "coder-agent",
"started_at": "2026-01-11T14:30:00Z"
}
context_files (lazy)deliverablescompletion_summary (max 200 chars)After agent signals completion:
acceptance_criteriabash
task-cli.ts complete {feature} {seq} "summary"
When completed_count == subtask_count:
status: "completed".tmp/tasks/{slug}/ → .tmp/tasks/completed/{slug}/| Status | Who Sets | When |
|---|---|---|
| pending | TaskManager | Initial creation |
| in_progress | Working agent | Picks up task |
| completed | TaskManager | After verification |
| blocked | Either | Dependency/issue found |
| Command | Use Case |
|---|---|
status |
Quick overview |
next |
What to work on |
parallel |
Batch parallel work |
deps |
Understand blockers |
blocked |
Identify issues |
complete |
Mark task done |
validate |
Health check |
../standards/task-schema.md - JSON field referencesplitting-tasks.md - How to create subtasks../lookup/task-commands.md - Full CLI reference