speckit-tasks

Generates dependency-ordered tasks.md checklists from spec-kit design artifacts.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/B18Bu/Refund-Agent --skill speckit-tasks-b18bu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/B18Bu/Refund-Agent/tree/main/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/B18Bu/Refund-Agent --skill speckit-tasks-b18bu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification and implementation plan into an actionable, ordered task list is manual and error-prone. This Skill automates the creation of a tasks.md file that organizes work by user story so each increment is independently implementable and testable. ## Core Features & Use Cases - Story-Organized Task Generation: Reads spec.md, plan.md, data-model.md, and contracts to produce phases per user story with strict checklist formatting (checkbox, task ID, [P] markers, [USn] labels, file paths). - Dependency and Parallelism Mapping: Outputs a dependency graph of story completion order plus parallel execution examples per story. - Extension Hook Support: Executes optional and mandatory pre/post hooks declared in .specify/extensions.yml before and after task generation. - Use Case: After drafting a spec and plan for a new checkout feature, run this Skill to produce a tasks.md with setup, foundational, per-story, and polish phases ready for incremental delivery. ## Quick Start Ask the agent to generate the tasks.md for the current feature based on the spec and plan in the .specify project structure.

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 feature specification?▼

Run the speckit-tasks Skill in a spec-kit project after creating spec.md and plan.md. It reads the design artifacts, organizes tasks by user story priority, and writes a tasks.md with checkbox-formatted tasks, IDs, and file paths.

What project structure does spec-kit task generation require?▼

It requires a .specify directory containing scripts/powershell/setup-tasks.ps1 and a feature directory with spec.md and plan.md. Optional documents like data-model.md, contracts/, research.md, and quickstart.md enrich the generated tasks.

How are tasks organized in the generated tasks.md?▼

Tasks are grouped into phases: Setup, Foundational prerequisites, one phase per user story in priority order, and a final Polish phase. Each story phase is independently testable and includes models, services, and endpoints for that story.

Does the task generator include test tasks automatically?▼

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 phases contain implementation tasks only.

What are extension hooks in spec-kit task generation?▼

Hooks are commands declared under hooks.before_tasks or hooks.after_tasks in .specify/extensions.yml. Mandatory hooks are executed automatically before or after generation, while optional hooks are only suggested to the user.