speckit-tasks

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

Updated Sep 12, 2026
One-click install
npx skills add https://github.com/AndyRace/heart-rate-graph --skill speckit-tasks-andyrace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/AndyRace/heart-rate-graph/tree/main/.github/skills/speckit-tasks
Command: npx skills add https://github.com/AndyRace/heart-rate-graph --skill speckit-tasks-andyrace

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, contracts, and research.md to produce tasks grouped by user story priority (P1, P2, P3). - Strict Checklist Format: Every task follows a validated format with checkbox, sequential task ID, parallelizable [P] markers, [US#] story labels, and exact file paths. - Dependency & Parallelism Analysis: Outputs a dependency graph of story completion order plus parallel execution examples and an MVP-first implementation strategy. - Extension Hooks: Supports pre- and post-execution hooks declared in .specify/extensions.yml, executing mandatory hooks and surfacing optional ones. - Use Case: After writing a spec and plan for a new feature in a spec-kit project, run this Skill to instantly get a complete tasks.md with setup, foundational, per-story, and polish phases ready for LLM-driven implementation. ## Quick Start Ask the agent to generate the tasks.md for the current feature based on the existing spec.md and plan.md 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 this Skill inside a spec-kit project after creating spec.md and plan.md. It executes the setup-tasks script, loads available design documents, and writes a tasks.md organized by user story with checkbox-formatted tasks, IDs, and file paths.

What documents are required to generate tasks with spec-kit?

Only 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 tasks generator work without a .specify directory?

No. The Skill requires a spec-kit project structure with a .specify directory containing the setup-tasks PowerShell script and templates. Without it, the setup step cannot resolve FEATURE_DIR or the tasks template.

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

No. Test tasks are optional and only generated when explicitly requested in the feature specification or when the user asks for a TDD approach. Otherwise phases contain models, services, endpoints, and integration tasks only.

What are extension hooks in spec-kit task generation?

Hooks are commands registered in .specify/extensions.yml under before_tasks or after_tasks. Mandatory hooks are executed automatically before or after generation, while optional hooks are surfaced as suggestions for the user to run.