speckit-tasks

To generate dependency-ordered task plans, you use a spec-kit project structure to extract feature plans and user stories, producing an actionable tasks.md file organized by user story phases with parallelization hints.

Specification-driven development task generation reads design artifacts like plan.md and spec.md to automatically outline implementation steps, moving teams from written specs to coding without manual task outlining.

Yes, you need a spec-kit project structure with .specify/ directories containing your design documents, which allows the system to execute prerequisite checks and derive the feature directory path.

Yes, you can automate task generation using before_tasks hooks defined in an extensions.yml file within your .specify directory to augment or gate the task generation process.

You organize implementation steps into independently testable phases by mapping prioritized user stories into sequential phases (P1, P2, P3) with clear dependency ordering and file-scoped instructions.

Creating a tasks.md file requires plan.md and spec.md design artifacts at minimum, while optionally reading data-model.md, contracts, research.md, and quickstart.md to produce tailored implementation tasks.