speckit-tasks

To generate dependency-ordered tasks from feature design documents, use a tool that parses your plan.md and spec.md files to produce a structured tasks.md. This output organizes work into setup, foundational, and per-story phases with explicit file paths and dependencies.

Breaking down a feature specification into test-driven development tasks involves creating a structured task plan that enforces TDD-style tests. The process reads your design artifacts and outputs a checkbox-based tasks.md file organized by foundational and per-user-story implementation phases.

Task generation from a spec.md without a plan.md is generally applicable, but the workflow is optimized for feature development that includes both. The process uses these design artifacts to validate completeness and output a structured task plan with a clear execution order.

Task tracking via tasks.md works by validating completeness with a strict, checkbox-based task format. It automatically organizes work items into setup, foundational, and per-user-story phases while providing parallel execution hints for independent tasks.

Generating a task plan from specifications does support parallel execution by producing parallel execution hints for independent tasks. The resulting tasks.md provides a clear execution order and explicit dependencies to guide your software engineering workflow.