speckit-tasks

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

Updated Aug 24, 2026
One-click install
npx skills add https://github.com/Fras0/clinics-api --skill speckit-tasks-fras0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/Fras0/clinics-api/tree/main/.cursor/skills/speckit-tasks
Command: npx skills add https://github.com/Fras0/clinics-api --skill speckit-tasks-fras0

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 that step by reading your spec-kit design documents and producing a structured tasks.md where every task is specific enough to execute without extra context. ## Core Features & Use Cases - Story-Organized Task Generation: Reads spec.md user stories with priorities and creates one phase per story, plus Setup, Foundational, and Polish phases. - Strict Checklist Format: Every task follows a validated format with checkbox, sequential task ID, parallel markers, story labels, and exact file paths. - Dependency & Parallelism Mapping: Produces a dependency graph of story completion order and identifies tasks that can run in parallel. - Extension Hooks: Supports optional and mandatory pre/post hooks declared in .specify/extensions.yml. - Use Case: After writing spec.md and plan.md for a new API feature, run this Skill to get a tasks.md with phases, MVP scope suggestion, and independent test criteria per story. ## Quick Start Ask the agent to generate the tasks.md for the current feature using the spec and plan in the .specify feature 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 executes the setup-tasks PowerShell script, loads spec.md and plan.md from the feature directory, and writes a tasks.md organized by user story with sequential task IDs and file paths.

What documents are required to generate implementation tasks?▼

plan.md and spec.md are required, providing the tech stack and prioritized user stories. Optional documents like data-model.md, contracts/, research.md, and quickstart.md enrich the generated tasks when present.

Does the task generator support test-driven development?▼

Tests are optional and only generated when explicitly requested in the feature specification or when the user asks for a TDD approach. By default, tasks focus on models, services, endpoints, and integration.

Can I run this Skill without a .specify directory?▼

No. The Skill requires a spec-kit project structure with a .specify/ directory, since it invokes .specify/scripts/powershell/setup-tasks.ps1 and reads design documents from the feature directory it returns.

Why are tasks organized by user story instead of by layer?▼

Organizing by user story makes each phase an independently testable increment, so stories can be implemented and validated in isolation. This enables MVP-first delivery and parallel work across stories.