speckit-tasks

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

1|Updated Aug 5, 2026
One-click install
npx skills add https://github.com/pieberrykinnie/hapa --skill speckit-tasks-pieberrykinnie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/pieberrykinnie/hapa/tree/main/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/pieberrykinnie/hapa --skill speckit-tasks-pieberrykinnie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning feature specifications and design documents into an actionable, ordered implementation plan is time-consuming and error-prone. This Skill automates the creation of a structured tasks.md file so every user story becomes a set of concrete, independently testable tasks. ## Core Features & Use Cases - Artifact-Driven Task Generation: Reads plan.md, spec.md, data-model.md, contracts/, and research.md from a spec-kit project to build tasks grounded in actual design decisions. - User-Story Organization: Groups tasks by prioritized user stories (P1, P2, P3) with dependency graphs, parallel execution markers, and MVP scope suggestions. - Strict Checklist Format: Enforces a consistent task format with IDs, [P] parallel markers, [USn] story labels, and exact file paths. - Extension Hooks: Supports optional and mandatory pre/post hooks defined in .specify/extensions.yml. - Use Case: After writing a feature spec and implementation plan in a spec-kit project, run this Skill to produce a tasks.md that an LLM or developer can execute task-by-task without extra context. ## Quick Start Ask the AI 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, then produces a tasks.md organized by user story with sequential task IDs, parallel markers, and file paths.

What is spec-kit task generation and how does it work?

Spec-kit task generation converts design artifacts (spec, plan, data model, contracts) into an executable checklist. Tasks are grouped into Setup, Foundational, per-story phases, and a Polish phase, each independently testable.

Does speckit-tasks work without a .specify directory?

No. The skill requires a spec-kit project structure with a .specify/ directory containing scripts, templates, and the feature's design documents. Without it, the setup script and template resolution cannot run.

What documents are required for task generation?

plan.md and spec.md are required for tech stack and user story priorities. data-model.md, contracts/, research.md, and quickstart.md are optional and enrich the generated tasks when present.

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

Organizing by user story makes each phase an independently testable increment, enabling MVP-first delivery and parallel work. Layer-based organization creates cross-story dependencies that block incremental delivery.