speckit-tasks

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-tasks generates a structured, dependency-ordered tasks.md for a feature based on available design artifacts, reducing manual planning effort.

Core Features & Use Cases

  • Generate an actionable, dependency-ordered tasks.md for a feature based on design artifacts like plan.md and spec.md.
  • Map user stories (P1, P2, etc.) from spec.md to tasks, with optional data-model.md, contracts/, research.md for richer context.
  • Produce a dependency graph, parallel execution examples, and an MVP-first rollout plan.

Quick Start

Place plan.md and spec.md in the feature directory and run speckit-tasks to generate tasks.md.

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 plan from spec.md and design artifacts?

A task plan generator reads spec.md and plan.md to produce a structured tasks.md file organized by user stories and dependency graphs. This automates mapping design artifacts into actionable development phases.

What is a spec-kit structure and when do I need a tasks.md file for it?

A spec-kit structure uses a .specify directory to hold plan.md and spec.md for feature planning. You need a tasks.md file when you want to convert these design artifacts into a dependency-aware development plan with parallelization opportunities.

How do I map user stories from spec.md to development tasks automatically?

You can map user stories to development tasks by running an automation tool that parses spec.md, extracts P1 and P2 stories, and generates a tasks.md file organizing them into a dependency-ordered execution plan.

Can I include data models and contracts when generating a task plan from design artifacts?

Yes, generating a task plan can optionally read data-model.md, contracts, and research.md files alongside spec.md. Including these artifacts provides richer context for the dependency graph and MVP-first rollout plan.

Does generating a tasks.md from spec-kit artifacts require any external dependencies?

Generating a tasks.md from spec-kit artifacts requires no external dependencies. You only need to place plan.md and spec.md in your feature directory for the tool to read and output the structured task plan.

What is the best way to identify MVP scope and parallelization opportunities from a feature spec?

The best way to identify MVP scope and parallelization opportunities is to generate a phase-based tasks.md from your spec.md. This produces a summary highlighting the MVP rollout plan and tasks that can run in parallel.