speckit-tasks

Generates dependency-aware tasks.md checklists from spec-kit implementation plans.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/alex-jordan547/agent-setup --skill speckit-tasks-alex-jordan547
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/alex-jordan547/agent-setup/tree/main/archive/speckit-tasks
Command: npx skills add https://github.com/alex-jordan547/agent-setup --skill speckit-tasks-alex-jordan547

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written implementation plan into an actionable, ordered task list is tedious and error-prone. This Skill automates the breakdown of spec-kit plans and specs into a structured tasks.md file with dependency-aware, independently testable tasks. ## Core Features & Use Cases - Plan-to-Task Generation: Reads plan.md, spec.md, data-model.md, contracts/, and research.md from a spec-kit feature directory and produces a complete tasks.md. - User Story Organization: Groups tasks by user story priority (P1, P2, P3) so each story phase is independently implementable and testable. - Strict Checklist Format: Enforces a consistent task format with checkboxes, sequential task IDs, [P] parallel markers, [USn] story labels, and exact file paths. - Use Case: After finishing a feature plan in a spec-kit project, run this Skill to generate a tasks.md with setup, foundational, per-story, and polish phases, plus a dependency graph and MVP scope suggestion. ## Quick Start Ask the agent to break down the current feature plan into a tasks.md task list using the spec-kit structure in this repository.

Frequently Asked Questions about speckit-tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a tasks.md from a spec-kit implementation plan?

Run the task generation workflow after planning: it reads plan.md and spec.md from the feature directory, maps entities and contracts to user stories, and writes a tasks.md organized by setup, foundational, per-story, and polish phases.

What task format does spec-kit tasks.md require?

Every task must follow the checklist format: a markdown checkbox, sequential task ID like T001, an optional [P] parallel marker, a [USn] story label for user story phases, and a description with an exact file path.

Does task generation require a spec-kit project structure?

Yes, it requires a spec-kit project with a .specify directory containing the check-prerequisites script and tasks template. It reads feature documents from the FEATURE_DIR resolved by that script.

Are test tasks always included in the generated task list?

No, test tasks are optional. They are only generated when explicitly requested in the feature specification or when the user asks for a TDD approach; otherwise only implementation tasks are produced.

How are tasks organized when a feature has multiple user stories?

Each user story from spec.md gets its own phase in priority order (P1, P2, P3), with models, services, and endpoints mapped to that story. This keeps every story independently implementable and testable, with a dependency graph showing completion order.