sdd-tasks

To turn a design doc into an actionable task checklist, you analyze change proposals and specs to generate a structured tasks.md with dependency-aware, ordered phases for engineers to follow.

Dependency-aware task sequencing is organizing implementation tasks by their logical dependencies, ensuring that prerequisite changes are validated and completed before subsequent phases begin in the generated checklist.

Yes, you can generate a tasks.md file directly from a change proposal and specs by analyzing the design artifacts and converting them into a concrete, ordered task breakdown aligned with openspec conventions.

No specific environment setup or dependencies are required. The tool independently analyzes your existing change proposals, specs, and design documents to produce the structured task checklist.

The best way to structure implementation phases is to parse the change request into a tasks.md document, breaking the work down into clearly labeled phases from proposal analysis to delivery.

You should not use automated task breakdown when your change proposal lacks concrete specs or design artifacts, as the tool requires these inputs to validate and sequence tasks accurately.