speckit-tasks

To generate a dependency-ordered tasks.md from spec-kit design artifacts, apply this Skill to a repository containing a .specify/ directory and design documents. It converts plan.md and spec.md files into phase-driven, user-story-aligned tasks with clear file paths.

Converting design documents into phase-based tasks works by reading feature specs and producing a checklist-format tasks.md organized by user stories. This output includes dependency ordering, parallelization notes, and a final polish phase, creating an immediately executable plan for AI implementation.

Yes, you need a .specify/ directory to generate user-story-aligned tasks with dependency order. This Skill is designed to apply specifically to spec-kit projects that include this directory structure alongside related design documents to produce properly formatted, executable task lists.

No, you cannot use this task generation process for projects without existing spec-kit artifacts. The Skill requires existing design documents like spec.md and plan.md within a .specify/ directory to map features into concrete, phase-based tasks with extension hooks.

The best way to structure task lists for parallelization and implementation phases is to organize tasks by user stories with clear dependency order. This Skill outputs a strict checklist format that includes parallelization notes and a final polish phase for an executable plan.

Limitations when converting feature designs into executable tasks.md files include strict adherence to spec-kit project structures. The Skill only processes repositories with a .specify/ directory and respects extension hooks, meaning non-spec-kit design formats are not supported.