sdd-tasks

Task breakdown for software projects maps dependencies, phases, and completion criteria from a change proposal into a repeatable blueprint. It organizes work into named phases with concrete tasks, checkbox tracking, and dependency ordering for execution.

The best way to manage dependencies and phases in a task blueprint is to generate a structured tasks.md file. This approach maps completion criteria and dependency ordering into clearly defined phases with checkboxes, creating a runnable plan for implementation teams.

To generate a tasks.md file for an openspec change, you apply the change proposal, specs, and design artifacts to the process. The output is a ready-to-run file placed under openspec/changes/{change-name}/tasks.md, structured into named phases with dependency ordering.

Yes, the task generation process works directly with existing design artifacts and specs. It takes these high-level inputs and transforms them into a concrete, structured plan suitable for software changes and feature tweaks.

You need to create a structured task blueprint for software engineering changes when you must transform high-level ideas into a runnable plan. This ensures implementation teams receive a concrete, actionable task list with mapped dependencies and completion criteria.