speckit-tasks

To turn design specs into an actionable task plan, you provide feature artifacts like plan.md and spec.md under a .specify directory. The tool reads these inputs and generates a dependency-ordered tasks.md document structured for phased execution.

Generating a dependency-ordered task list from spec.md requires placing the file in a .specify directory. The system maps the design artifacts into a phased workflow with explicit task IDs and outputs a checklist-formatted tasks document.

The best way to structure feature implementation tasks from a spec-kit is mapping them into Setup, Foundational, User Story, and Polish phases. This dependency-ordered structure enables parallel execution where possible and aligns teams with plan artifacts.

Yes, you need a .specify directory structure to generate a phased task workflow. The system validates prerequisites by reading plan.md and spec.md from this directory, along with optional artifacts like data-model.md and contracts, to build the executable task outline.

Yes, you can use optional design artifacts like data-model.md, research.md, and files in a contracts directory to enrich generated tasks. The system reads these alongside plan.md to enhance task traceability and provide deeper context for feature implementation.

Generated tasks are organized into Setup and Foundational phases to build a dependency graph and ensure proper sequencing. This structure validates prerequisites first, enabling parallel execution of user story phases later in the implementation workflow.