speckit-tasks

To generate a tasks.md from design artifacts, the skill reads plan.md and spec.md from your FEATURE_DIR, assembles a dependency-ordered task outline, and enforces a strict checklist format associating tasks with user stories.

User stories are organized into a phased task plan: Phase 1 handles Setup, Phase 2 covers Foundational tasks, and Phase 3+ dedicates one phase per user story in priority order, concluding with a Final Phase for polish.

Yes, you can use optional documents to generate actionable task instructions; the skill reads data-model.md, contracts/, research/, and quickstart.md alongside required files to enrich the task plan.

To identify MVP scope and parallelization opportunities, the generated task plan includes a dependencies graph, parallel execution examples, and a report detailing total task count and per-story breakdown.

Generating a tasks.md requires a FEATURE_DIR containing plan.md for tech stack details and spec.md for user stories; no external dependencies are needed to process these design artifacts.

Tasks not following the required checklist format occur when design artifacts lack clear user story priorities; the skill validates the output and reports formatting to ensure strict checklist compliance.