TASKS.md
Agent-ready task system
Decompose the plan into dependency-ordered work units with explicit inputs, scope, outputs, acceptance checks, ownership, status, and integration evidence suitable for people or delegated agents.
Fillable structure
Replace prompts with project evidence.
Remove any field that does not apply. A smaller maintained file is more useful than generic documentation that agents and reviewers cannot trust.
- 01
Task contract
Use the same minimum outcome, scope, and verification contract for every work item.
Outcome: State the artifact or state change that completes the task
Inputs and scope: List required context, allowed paths, dependencies, and explicit exclusions
Acceptance: Define commands, tests, inspection, or evidence that verifies the output
- 02
Phases and dependencies
Keep the executable queue aligned with the plan and specification.
Setup: List environment and harness tasks that unblock later work
Foundational: List shared contracts, data, security, and architecture tasks
Delivery phases: Group vertical work by user outcome and mark parallel-safe tasks
- 03
Work queue
Make state, ownership, and handoffs visible without hiding unfinished work.
Ready: List unblocked tasks with owner and priority
In progress: List active tasks, current evidence, and blocking questions
Done: Record verification evidence, integration result, and links to changes
- 04
Integration and convergence
Check the complete integrated outcome after every individual task and local verification passes.
Integration order: State merge, migration, release, and cross-task verification order
Gap analysis: Compare completed work with the specification, plan, and acceptance checks
Follow-up: Append discovered gaps with owners rather than hiding them in completion notes
Related field guides
Next template
CONTEXT.md · Context engineering system