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/KarenTenorio963/curso-mcp-karentenorio --skill speckit-tasks-karentenorio963
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/KarenTenorio963/curso-mcp-karentenorio/tree/main/entregas/s4/mi-proyecto-speckit/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/KarenTenorio963/curso-mcp-karentenorio --skill speckit-tasks-karentenorio963

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification and implementation plan into an actionable, ordered task list is slow 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 - Artifact-Driven Task Generation: Reads plan.md, spec.md, data-model.md, contracts/, and research.md from a spec-kit feature directory to derive concrete tasks with exact file paths. - User Story Organization: Produces phases per user story in priority order, with dependency graphs, parallel execution markers, and MVP scope suggestions. - Extension Hook Support: Executes optional and mandatory pre/post hooks defined in .specify/extensions.yml before and after task generation. - Use Case: After writing a spec and plan for a new API feature, run this Skill to get a tasks.md where every task follows a strict checklist format (checkbox, task ID, story label, file path) ready for an LLM or developer to execute. ## Quick Start Ask the agent to generate the tasks.md for the current feature using the spec and plan in the spec-kit project.

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 inside a spec-kit project. It executes setup-tasks.ps1 to locate the feature directory, loads spec.md and plan.md, and writes a tasks.md organized by user story with checkbox-formatted tasks and file paths.

What is spec-kit task generation by user story?▼

It is a task organization method where each user story from spec.md gets its own phase containing the models, services, and endpoints it needs. This makes every phase an independently testable increment, with setup and foundational tasks handled first.

Does speckit-tasks require a spec-kit project structure?▼

Yes, it requires a .specify/ directory with the setup-tasks.ps1 script and a feature directory containing at least spec.md and plan.md. Optional documents like data-model.md, contracts/, and research.md enrich the generated tasks.

Are test tasks always included in the generated tasks.md?▼

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 format must tasks follow in tasks.md?▼

Every task must be a markdown checkbox with a sequential task ID, an optional [P] parallel marker, a story label like [US1] for user story phases, and a description with an exact file path. Tasks missing any component fail validation.