sdd-tasks

Generating actionable tasks from change proposals requires converting specs and designs into a structured, phase-based tasks.md file. This skill automates that breakdown, producing concrete implementation and testing tasks traceable across project phases.

Phase-based task breakdown organizes implementation work into sequential stages, typically Phase 1 through Phase 4. It transforms specs and design documents into structured tasks.md outputs, ensuring changes are actionable, traceable, and coordinated across project phases.

Creating a tasks.md checklist for a system rewrite involves structuring change proposals into phase-based tasks. You provide the change name and relevant documents, and the skill outputs a ready-to-use, structured task breakdown formatted for implementation and testing.

Yes, generated task checklists can be persisted in Engram or OpenSpec backends. The skill ensures the output tasks.md adheres to the required sdd task format, supporting direct integration with these storage workflows and project coordination environments.

Generating phase-based tasks supports software changes, feature updates, and system rewrites. The skill applies change proposals and specs to produce concrete, actionable tasks formatted for implementation and testing across all defined phases.

You need to provide the change name and relevant design or specification documents. No dependencies are required; the skill processes these inputs to automatically output a ready-to-use, structured tasks.md file formatted for project coordination.