| name | sdlc-tasks |
| description | Phase 3 of the SDLC. Use this to break an approved plan into an ordered list of small, independently testable tasks ready for implementation. Triggers after plan.md exists. Produces specs/<feature>/tasks.md where each task has a clear definition of done and maps to acceptance criteria. Each task should be completable and verifiable on its own. |
Phase 3 — Tasks (ordered, testable units)
Decompose the plan into a build order an agent can execute one task at a time.
Preconditions
specs/<feature>/plan.md exists. If not, route to /plan.
Process
- Read
plan.md + spec.md acceptance criteria.
- Produce
specs/<feature>/tasks.md from templates/tasks.template.md. Each task:
- has a stable ID (T001, T002, …),
- states its definition of done (the failing test it must make pass),
- lists dependencies on other tasks,
- is small enough to finish in one focused step,
- maps back to a spec acceptance criterion or ADR.
- Order tasks so dependencies come first; mark parallelizable tasks
[P].
Quality bar
- No task says "implement everything." If a task is vague, split it.
- Every acceptance criterion in spec.md is covered by at least one task.
Exit
Update .sdlc/state.json (phase=tasks). Persist checkpoint. Say: "Tasks ready. Next: /design (if UI) or /implement."
Примітка (UK)
Кожна задача має чітке "визначення готовності" (тест, який треба зробити зеленим) і
посилається на критерій приймання зі специфікації. Жодних розмитих "зробити все".
