speckit-tasks

Generate a dependency-ordered tasks.md from design artifacts for spec-kit projects.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/burningddol/epigram --skill speckit-tasks-burningddol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/burningddol/epigram/tree/main/.claude/skills/speckit-tasks
Command: npx skills add https://github.com/burningddol/epigram --skill speckit-tasks-burningddol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-tasks solves the problem of turning design artifacts into concrete, executable work items by generating a dependency-aware tasks.md that maps user stories to actions across project phases.

Core Features & Use Cases

  • Generate a tasks.md organized by user stories from plan.md, spec.md, data-model.md, contracts, and research docs when present.
  • Produce a dependency graph, phase-based structure, and MVP guidance to support incremental delivery.
  • Output a summary including total tasks and per-story counts for planning and tracking.

Quick Start

Run speckit-tasks in your project directory to generate tasks.md from the design artifacts.

Frequently Asked Questions about speckit-tasks

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

FAQPage Schema
How do I convert design artifacts into actionable tasks?

Generating a tasks.md from design artifacts maps user stories from plan.md, spec.md, and data-model.md to concrete, dependency-ordered actions. This produces a structured document with phase-based task breakdowns to guide feature implementation.

How do I generate a dependency graph for project tasks?

A dependency graph for project tasks is generated by mapping user stories to concrete actions across project phases. This creates a dependency-ordered structure that defines execution sequence and provides MVP guidance for incremental delivery.

What is a dependency-ordered tasks document for user stories?

A dependency-ordered tasks document maps user stories to concrete actions across project phases using a strict task format. It includes a dependency graph and MVP guidance to support structured, incremental feature delivery from design artifacts.

Do I need spec-kit style project files to generate a task list?

You need spec-kit style project files like plan.md, spec.md, data-model.md, contracts, and research docs to generate a task list. These design artifacts are parsed to map user stories into dependency-ordered, actionable work items.

Can I get a task count summary from design artifacts?

Generating a tasks document from design artifacts outputs a summary including total tasks and per-story counts. This summary provides planning and tracking metrics for monitoring feature implementation progress across project phases.

When should I not use automated task generation from design specs?

Automated task generation from design specs is not suitable when standard design artifacts like plan.md, spec.md, or data-model.md are absent. The mechanism requires these files to successfully map user stories to dependency-ordered implementation actions.