speckit-tasks

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

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/MagnoAlves1993/handy --skill speckit-tasks-magnoalves1993
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/MagnoAlves1993/handy/tree/main/.github/skills/speckit-tasks
Command: npx skills add https://github.com/MagnoAlves1993/handy --skill speckit-tasks-magnoalves1993

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification and implementation plan into an actionable, ordered task list is tedious 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, parallelization marker, story label, and exact file path. - Dependency & Parallelism Analysis: Produces a dependency graph, parallel execution examples per story, and an MVP-first implementation strategy. - Extension Hooks: Supports optional and mandatory pre/post hooks declared in .specify/extensions.yml. - Use Case: After writing a spec and plan for a new feature with GitHub Spec Kit, run this Skill to instantly get a complete tasks.md ready for LLM-driven implementation. ## Quick Start Ask the AI to generate the tasks.md for the current feature based on the spec and plan in the specs 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, then produces a tasks.md with phases for setup, foundational work, and one phase per user story in priority order.

What is the task checklist format in GitHub Spec Kit?

Every task must follow the format: checkbox, sequential task ID like T001, optional [P] parallel marker, optional story label like [US1], and a description with an exact file path. Tasks missing any required component are rejected during validation.

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

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

Are test tasks generated automatically in 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 only implementation tasks.

What are extension hooks in spec-kit task generation?

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