speckit-tasks

To generate a dependency-ordered task plan, speckit-tasks reads plan.md and spec.md to produce a phase-driven tasks.md with mapped tasks per user story. It automatically structures your project setup into phases like Setup, Foundational, US1, and Final.

Automating user story task breakdown involves converting design artifacts into an executable checklist organized by phases and user stories. This process eliminates ambiguity and accelerates delivery by enforcing dependency order, parallelism, and a final polish phase.

Yes, speckit-tasks supports optional inputs including data-model.md, contracts/, and research.md to enrich task mapping. These additional design artifacts help refine the generated phase-based task breakdown and ensure better traceability to your MVP scope.

Stale-task detection and build-order tracking work by embedding pin-hash metadata within the generated tasks.md file. This pin-backed structure allows the system to identify outdated tasks and maintain an accurate build-order integration throughout the project lifecycle.

Phase-driven task planning relies heavily on aligning tasks with a defined MVP scope and user stories for traceability. While you can generate a tasks.md without strict MVP boundaries, the resulting dependency order and phase structure are optimized for projects with clear scope definitions.