speckit-tasks

To generate a dependency-ordered task roadmap, the tool reads design artifacts like plan.md, spec.md, data-model.md, and contracts to produce an actionable tasks.md file. It structures tasks into phased workflows and provides MVP scope guidance.

A spec-kit driven project layout uses a .specify directory containing design artifacts and templates. This structure allows the tool to automatically parse plan.md, spec.md, and contracts to enforce a phased workflow and generate a structured tasks.md file.

You structure tasks into phases by running the tool against your .specify directory. It enforces a phased workflow including Setup, Foundational, User Story phases, and Polish, automatically ordering dependencies within the generated tasks.md file.

Yes, you can use extension hooks during task generation by configuring a .specify/extensions.yml file. This allows you to define and execute custom pre-generation and post-generation tasks within your spec-kit driven project workflow.

Yes, the generated tasks.md includes project summaries and MVP guidance. It outputs a concise summary featuring total task count, per-story task counts, dependency mappings, and the defined MVP scope for the project.

Before generating a tasks.md file, you need plan.md, spec.md, data-model.md, and contracts available within your .specify directory. These design artifacts provide the necessary structure and dependencies for the tool to create the roadmap.