speckit-tasks

To generate a dependency-ordered task list, the skill reads your repository's plan.md and spec.md files to produce a tasks.md checklist organized by priority-based user stories. It organizes work into setup, foundational, and user-story phases with independent test criteria.

You need plan.md and spec.md files to generate a tasks.md checklist, along with the .specify directory structure. The generator optionally reads data-model.md, contracts/, research.md, and quickstart.md to tailor tasks to your available design artifacts.

A dependency graph improves user story task generation by building a completion-order workflow across user stories. This ensures each phase is independently testable and provides parallel execution suggestions for implementing the feature design.

Yes, you can use extension hooks to customize tasks.md generation by defining optional and mandatory pre- and post-generation hooks in your .specify/extensions.yml file. The generator runs these hooks without evaluating their internal conditions.

Yes, spec-kit task generation enforces a strict checklist format in the output tasks.md file. It strictly follows the required checklist schema, ensuring generated tasks include specific file paths and conform to spec-kit project structure expectations.

You should not use automated user story task generation if your repository lacks the required plan.md and spec.md design artifacts or the necessary .specify directory structure. The tool depends on these files to map dependencies and produce accurate implementation phases.