tasks
Tasks — turn an approved plan into a verifiable work list
The tasks phase is the hinge between thinking and doing. The plan already
decided the architecture, the interfaces, and the testing strategy. This phase
slices that plan into the smallest units a coding agent can finish, prove, and
hand off — each one ordered, each one carrying a done-check that a machine or
a reviewer can run without trusting anyone's word.
A task list is not a to-do list. A to-do list says "build the auth endpoint". A
task list says "T004: implement POST /login; done when pytest tests/auth/test_login.py is green AND a 401 is returned for a bad password —
depends on T002, T003; parallel-safe with T005." The difference is that the
second one can be handed to a subagent, executed, and verified with no
further questions. This phase writes zero runtime code; it produces one artifact,
appended to the plan it was built from.