sdd-tasks

To generate a task breakdown, provide the change name and design inputs to create a deterministic tasks.md file. This file organizes implementation into sequential phases with actionable, testable items and explicit file path references.

Structuring tasks by phases enforces a logical dependency sequence from proposal through design to implementation. The breakdown organizes actions sequentially from Phase 1 to Phase 4, ensuring developers follow strict project conventions and order.

Yes, you can use openspec standards to create deterministic task checklists. The generated tasks.md aligns with project conventions, producing repeatable and testable implementation steps that guide developers through the software change process.

You can enforce dependency order by generating a tasks.md file that references concrete file paths within each sequential phase. This structural mapping ensures actionable items are executed in the correct logical sequence.

You need a designated change-name and its corresponding design inputs. These inputs are processed to emit the final openspec/changes/{change-name}/tasks.md file containing the structured, actionable task breakdown.

Yes, the task breakdown generation produces repeatable, convention-aware templates. These templates provide deterministic outputs that can be reused to quickly structure implementation checklists for similar software modifications.