sdd-implementation

Spec-driven development executes planned implementations by loading plan.md, spec.md, tasks.md, and todo-list.md from the active specs directory. It translates these formal specs into actionable steps, processes tasks in dependency order, and maintains traceability with completion markers to reduce drift between planning and delivery.

Spec-driven development orchestrates code generation by translating formal specs into actionable todo-lists and executing tasks sequentially. It enforces sequential execution, marks completed items, records blockers, and maintains alignment between your development work and the defined plan.

Yes, this plan execution workflow updates the todo-list as work progresses, marking completed items and recording any blockers encountered. You can monitor ongoing progress using the progress.sh script and verify final results with sdd-verifier after completion.

Yes, plan-driven feature building requires formal spec documents located in specs/active/[task-id]/. You must generate a complete roadmap containing plan.md, spec.md, tasks.md, and todo-list.md before beginning execution to ensure proper sequential task processing.

Start by generating a complete roadmap using a full-plan command for your feature, then begin execution to process the generated tasks in dependency order. As execution proceeds, the workflow updates the todo-list, tracks progress via progress.sh, and validates results with sdd-verifier.

Drift occurs when development work lacks strict alignment with defined plans. This skill solves drift by loading formal specs, enforcing sequential execution in dependency order, and maintaining traceability through completion markers and recorded blockers throughout the feature building process.