speckit-tasks

To generate actionable tasks from design artifacts, parse plan.md, spec.md, data-model.md, and contracts to produce a dependency-ordered tasks.md organized by user story and implementation phase. This removes ambiguity about execution order and testing criteria.

The spec-kit structure uses a .specify directory to store plan.md, spec.md, optional data-model.md, and contracts. Task generation parses these artifacts to emit checklist-formatted tasks, dependency graphs, and parallelization notes for developer-ready increments.

You can organize user stories into a dependency graph by parsing design artifacts and enforcing a phase-based workflow: Setup, Foundational, User Stories, and Polish. This generates a dependency-ordered tasks.md with strict checklist formatting, file paths, and IDs.

Yes, you can generate an MVP recommendation by parsing check-prerequisites output and converting plan.md and spec.md artifacts into independent implementation increments, reporting task counts and dependencies to identify the minimum viable scope.

Yes, task generation detects and respects before/after extension hooks. It parses the check-prerequisites output to enforce strict checklist formatting while honoring phase-based workflow boundaries and reporting pre/post hook dependencies.

Automated task generation requires a valid spec-kit project with a .specify directory containing plan.md and spec.md. Without these specific design artifacts, the Skill cannot produce dependency-ordered tasks.md or report parallelization notes.