sdd-tasks

To break down a software change proposal, provide the proposal, spec, and design documents to generate a structured tasks.md file. The output organizes implementation tasks by phase with concrete, testable steps and clear dependencies for engineers.

Yes, you can automatically generate a task checklist from design documents. The system analyzes your specs and proposals to produce an organized tasks.md file or an in-memory task structure, depending on your selected persistence mode.

Organizing implementation tasks by phase is handled automatically by analyzing your proposal and design documents. The generated task breakdown structures each phase with clear acceptance criteria and explicit dependencies for seamless execution.

You do not strictly need a tasks.md file, as the breakdown can be persisted as an in-memory task structure. However, generating a tasks.md file allows you to directly share and integrate the actionable task plan within engineering workflows.

Yes, the task breakdown integrates directly with Engram and openspec workflows. This integration allows you to persist and share the generated implementation task plan seamlessly across your existing engineering automation pipeline.

Manual implementation tasks often lack clear acceptance criteria because they are not systematically derived from specs. Automatically generating the breakdown from design documents ensures every task includes concrete, testable steps and explicit dependencies.