Generate an actionable, dependency-ordered task list from the feature spec and plan.
Input: Optionally specify a change name. If omitted, infer from context or ask.
Steps
- Load artifacts Required:
specs/changes/<name>/plan.mdandspecs/changes/<name>/spec.md. Optional (also load if present):specs/changes/<name>/checklists/. If plan.md is missing, prompt to use thespec-kit-planskill first. - Generate
specs/changes/<name>/tasks.mdStructure tasks in phases:# Tasks: <Feature Name> ## Phase 1: Setup & Foundations - [] [T01] Description with exact file path ## Phase 2: Domain & Application Layer - [] [T02] Description with exact file path - [] [T03] [P] Description (parallel — can run concurrently with T02) ## Phase 3: Infrastructure & Adapters - [] [T04] [P] Description with exact file path ## Phase 4: Integration & Validation - [] [T05] Description with exact file path ## Dependency Graph T01 → T02 → T04 → T05 ↘ T03 ↗ ## MVP Scope <Minimum set of tasks for a working, deployable slice.>Task format:- [] [TaskID] [P?] [Story?] Description with exact file path
- [P] marks tasks safe to run in parallel. - Each task must be specific and immediately executable. - Order: setup → domain → application → infrastructure → integration → polish. - Map each task back to a user story from spec.md.
- Validate Before finishing:
- Every user story has at least one task. - All tasks include exact file paths. - No task is vague or unbounded.
Output
After writing tasks.md:
- Task count per phase.
- MVP scope summary.
- Next step: "Use the
spec-kit-implementskill to execute the task list."
Guardrails
- If unresolved FRAMEWORK.md violations exist from the
spec-kit-analyseskill, warn before generating tasks. - Never generate tasks that violate the dependency rule.
- Domain and application tasks must precede infrastructure tasks in ordering.