speckit-tasks

Generate dependency-ordered implementation tasks from plan.md and spec.md into tasks.md.

1|Updated Jun 16, 2025
One-click install
npx skills add https://github.com/imbatony/pavone --skill speckit-tasks-imbatony
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/imbatony/pavone/tree/main/.claude/skills/speckit-tasks
Command: npx skills add https://github.com/imbatony/pavone --skill speckit-tasks-imbatony

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts available design artifacts into concrete, actionable development tasks organized by dependencies, eliminating ambiguity and the manual effort of decomposing specifications into execution-ready checklists.

Core Features & Use Cases

  • Design-driven task generation: Loads plan.md, spec.md, optional data-model.md, contracts, research.md, and quickstart.md to derive implementation work.
  • Structured phases and dependency ordering: Produces Phase 1 (setup), Phase 2 (foundation), Phase 3+ (per-user-story) sections, a dependency graph, and per-story task lists with IDs and file paths.
  • Hook awareness and reporting: Detects .specify/extensions.yml hooks and emits optional or required hook instructions without evaluating conditional expressions.
  • Use case: Product managers and engineering teams run this on a spec-kit project to get an immediately executable tasks.md that LLMs or humans can follow for incremental delivery.

Quick Start

Use the speckit-tasks skill to generate a dependency-ordered tasks.md from a repository that contains a .specify directory and spec.md files.

Frequently Asked Questions about speckit-tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate dependency-ordered implementation tasks from project design artifacts?

To generate dependency-ordered implementation tasks, load design artifacts like plan.md and spec.md into a spec-kit project structure. This produces a tasks.md file organized by phases and user stories with checklists, IDs, and file paths.

What is a spec-kit project structure for task generation?

A spec-kit project structure for task generation uses a .specify directory containing spec.md, plan.md, and optional files like data-model.md and research.md. It serves as the source for deriving actionable, dependency-ordered development checklists.

How do I create an actionable tasks.md checklist from user stories?

You can create an actionable tasks.md checklist from user stories by processing spec.md and plan.md files. The output organizes tasks into phases with unique IDs, story tags, file paths, and a dependency graph for incremental delivery.

Does task generation work with .specify extensions.yml hooks?

Yes, task generation works with .specify extensions.yml hooks by detecting them during processing. It emits optional or required hook instructions directly into the tasks.md file without evaluating conditional expressions.

Can I use generated tasks.md for LLM-driven execution?

Yes, you can use the generated tasks.md for LLM-driven execution. It produces checklist-form tasks with dependency graphs, parallelization markers, and a summary specifically suitable for LLMs or humans to follow for incremental delivery.

What limitations exist when generating a dependency graph from design documents?

A limitation when generating a dependency graph is that it requires a spec-kit project structure with a .specify directory. It processes available design artifacts but does not evaluate conditional expressions within .specify extensions.yml hooks.