speckit-tasks

Generate dependency-ordered tasks.md from plan.md and spec.md design artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts. This helps teams turn design plans into a concrete, executable task list that aligns with project structure and priorities.

Core Features & Use Cases

  • Load plan.md (tech stack, libraries, structure), spec.md (user stories with priorities), and optional artifacts (data-model, contracts, research, quickstart) to drive task creation.
  • Organize tasks into phases: Setup, Foundational, and per-user-story phases in priority order, with a final polish phase, including a dependency graph and parallel-execution hints.
  • Produce a ready-to-run tasks.md using the specified template, including file paths, dependencies, and MVP guidance for the first user story.

Quick Start

Run the speckit-tasks skill against your repository to generate a tasks.md from the available 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 generate a dependency-ordered task list from design artifacts?

You generate a dependency-ordered tasks.md by loading design artifacts like plan.md and spec.md, mapping them to user stories, and organizing the output into setup, foundational, and feature phases with parallel-execution hints.

How do I turn spec.md user stories into actionable sprint planning tasks?

You turn spec.md user stories into sprint planning tasks by mapping story priorities to development phases. This produces a concrete tasks.md featuring file paths, dependency graphs, and MVP guidance for the first user story.

Does this task generation approach work without a strict spec-kit project structure?

No, this task generation approach requires a spec-kit project structure. It specifically relies on having a plan.md for tech stack details and a spec.md for prioritized user stories to correctly map artifacts and validate task completeness.

What is the best way to organize feature development phases from project setup to polish?

The best way to organize feature development phases is to sequence them as Setup, Foundational, per-user-story phases in priority order, and a final polish phase, ensuring a dependency graph validates task completeness across the project.

Can I include optional documents like data models and contracts when generating a project task list?

Yes, you can include optional documents like data models, contracts, research, and quickstart guides when generating a project task list. These artifacts are loaded alongside plan.md to drive more accurate task creation and dependency mapping.

Why are my generated project tasks missing parallel-execution hints and file paths?

Your generated project tasks may miss parallel-execution hints and file paths if the input design artifacts lack sufficient technical detail. The system extracts tech stack and structure data from plan.md to populate these specific fields.