sdd-tasks

To break down a software change into actionable engineering tasks, provide an orchestrator with the change name and artifact mode to generate a structured, phase-driven tasks.md checklist from design proposals and specifications.

Generating a task checklist from design specifications involves consuming design artifacts like proposals and specs to derive concrete actions, outputting a ready-to-use tasks.md document organized by implementation phases with checkboxes.

Yes, this task breakdown method supports engram, openspec, and none artifact modes, reading persistence contracts and external conventions to generate phase-driven task lists while respecting the specified storage and persistence rules.

Yes, you can create a tasks.md file without modifying existing project files by setting the artifact mode to none, which outputs a ready-to-use task checklist without altering your current file structure or persistence contracts.

Providing an artifact mode is required to generate a task breakdown because it determines how persistence contracts and external conventions are read, ensuring the resulting phase-driven tasks.md aligns with your specific engineering workflow.

When artifact mode is none, the limitation is that the tool outputs the generated tasks.md without modifying files or reading external conventions, relying solely on the provided design proposals and specifications to derive the task breakdown.