speckit-tasks

Generate a dependency-ordered tasks.md from plan and spec documents.

Updated Jun 8, 2025
One-click install
npx skills add https://github.com/cicero78M/Cicero_Web --skill speckit-tasks-cicero78m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/cicero78M/Cicero_Web/tree/main/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/cicero78M/Cicero_Web --skill speckit-tasks-cicero78m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams transform design artifacts into a ready-to-execute tasks.md, ensuring a clear, dependency-aware plan for feature implementation.

Core Features & Use Cases

  • Automates extraction of plans from plan.md, spec.md, and data-model.md (if present) to build a phased tasks document.
  • Generates a dependency graph and aligns tasks with user stories (US1, US2, etc.), while ensuring every task follows the strict checklist format.
  • Produces a ready-to-run tasks.md and a high-level summary of total tasks, per-story breakdown, and MVP scope.

Quick Start

Run the speckit-tasks tool to generate tasks.md from plan.md and spec.md in the project root.

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

To generate a tasks.md from design artifacts, run the tool in your project root. It extracts user stories, data models, and interfaces from plan.md and spec.md, then outputs a dependency-ordered task list with a high-level summary.

What is the best way to create a dependency graph for feature implementation tasks?▼

Creating a dependency graph for feature tasks is automated by mapping user stories, data models, and interfaces to concrete tasks. It builds the dependency graph from your design artifacts and enforces a strict checklist format for every generated task.

Do I need a .specify directory to generate user story task plans?▼

Yes, you need a .specify directory in your project. The tool requires plan.md and spec.md documents within this structure to map user stories and data models into a phased, dependency-aware tasks.md file.

Can I align generated tasks with specific user stories like US1 and US2?▼

Yes, aligning generated tasks with user stories like US1 and US2 is supported. The tool maps extracted user stories to concrete tasks and produces a per-story breakdown along with the total task count and MVP scope in the summary.

How does the spec-kit task generation handle data models and interfaces?▼

Spec-kit task generation handles data models and interfaces by extracting them from available design artifacts like data-model.md. It maps these technical definitions to concrete tasks, ensuring the generated tasks.md reflects your project's actual architecture and dependencies.

What format does the generated tasks.md follow for each task?▼

The generated tasks.md enforces a strict checklist format for each task. This ensures every task derived from your user stories and design artifacts is actionable and consistently structured within the dependency-ordered document.