speckit-tasks

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

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Carl-Fabri/TestAngularSpecDriven --skill speckit-tasks-carl-fabri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/Carl-Fabri/TestAngularSpecDriven/tree/main/test-angular/.claude/skills/speckit-tasks
Command: npx skills add https://github.com/Carl-Fabri/TestAngularSpecDriven --skill speckit-tasks-carl-fabri

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 with clear dependencies and parallelization opportunities. ## Core Features & Use Cases - Automated Task Generation: Reads plan.md, spec.md, data-model.md, contracts, and research.md from a spec-kit project to produce a structured tasks.md. - User Story Organization: Groups tasks by prioritized user stories (P1, P2, P3) so each story is independently implementable and testable. - Strict Checklist Format: Enforces a consistent task format with IDs, parallel markers, story labels, and exact file paths. - Use Case: After writing a spec and plan for a new feature, run this Skill to instantly get a complete tasks.md with setup, foundational, per-story, and polish phases ready for execution. ## Quick Start Ask the assistant to generate the tasks.md for the current feature based on the spec and plan in the .specify directory.

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. It reads spec.md and plan.md from the feature directory, extracts user stories and tech stack, and writes a tasks.md organized by story with dependencies and parallel execution examples.

What files does spec-kit task generation require?

It requires plan.md and spec.md in the feature directory. Optional inputs include data-model.md, contracts/, research.md, and quickstart.md, which enrich the generated tasks when present.

Does the tasks generator work without a .specify directory?

No. The skill requires a spec-kit project structure with a .specify directory containing scripts and templates. It runs setup-tasks.ps1 from .specify/scripts to locate the feature directory and tasks template.

How are tasks organized in the generated tasks.md?

Tasks are grouped into phases: Setup, Foundational, one phase per user story in priority order, and a final Polish phase. Each task follows a strict checklist format with an ID, optional parallel marker, story label, and file path.

Are test tasks always included in the generated task list?

No. Test tasks are optional and only generated when explicitly requested in the feature specification or when the user asks for a TDD approach.