speckit-tasks

Run the speckit-tasks Skill in a project with a .specify directory containing spec.md and plan.md. It parses user stories with priorities, maps entities and contracts to stories, and outputs a phase-organized tasks.md with sequential task IDs and file paths.

Spec-kit task generation converts design documents into an executable checklist organized by user story. The Skill runs a PowerShell setup script to locate the feature directory, loads available design docs, and emits tasks in a strict checkbox format with dependency ordering.

Yes, only plan.md and spec.md are required. Data-model.md, contracts, research.md, and quickstart.md are optional inputs that enrich task generation when present, and the Skill adapts to whatever documents exist in the feature directory.

Story labels like [US1] are only applied to user story phase tasks, never to Setup, Foundational, or Polish phases. If labels are missing inside a story phase, the spec.md may lack properly prioritized user stories for the Skill to map.

Avoid it when the feature lacks a written spec or plan, since the Skill depends on those artifacts for story extraction. It is also less useful for one-off scripts or exploratory work where formal phase breakdown adds overhead without benefit.