sdd:tasks

Generating a task list from a feature spec involves reading spec.md and plan.md from the specs/ directory, applying phase rules to sequence core tasks first, and writing the lean actionable list to tasks.md using a template.

Spec-driven development task generation translates a feature spec and plan into a lean, actionable task list. You need it to accelerate the handoff from design to development while maintaining workflow traceability via transition logs.

You can generate tasks.md in both auto and manual modes. The workflow supports either mode to produce the phased task list and update the workflow state in .spec-context.json with progress and transition logs.

The workflow enforces phase rules by assigning phase order to ensure core tasks execute first, marking optional parallel groups with [P], and identifying gating tasks before updating .spec-context.json with the resulting progress.

You need a feature spec.md and a plan.md inside a numbered specs/ directory, along with a .spec-context.json file. The workflow reads these inputs to fill the tasks.md template and append transition logs.