speckit-tasks

Convert plan.md and spec.md into dependency-aware task lists.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks implementation plans and specifications into precise, actionable task lists that are immediately executable and testable, removing ambiguity from project handoffs and planning artifacts.

Core Features & Use Cases

  • Structured Task Generation: Converts plan.md and spec.md content into phased tasks organized by user story, with explicit file paths and checklist-style task IDs.
  • Dependency Awareness & Parallelization: Produces a dependency graph and marks parallelizable tasks to enable safe concurrent work and clear story ordering.
  • Validation & Deliverables: Validates checklist format, generates a tasks.md using a template, summarizes task counts per story, and suggests an MVP scope for incremental delivery.
  • Use Case: Ideal for teams using spec-kit project structure to transform design docs into independent, testable development increments.

Quick Start

Run the speckit-tasks skill with the project's feature directory to produce a dependency-aware tasks.md ready for implementation.

Frequently Asked Questions about speckit-tasks

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

FAQPage Schema
How do I generate ordered, executable tasks from a spec-kit implementation plan?

To generate ordered tasks from a spec-kit plan, the skill parses plan.md and spec.md to produce a tasks.md file containing dependency-aware, checklist-style task IDs organized by user story for immediate execution.

How do I create a dependency graph for parallel task execution from project specifications?

Creating a dependency graph for parallel execution involves analyzing spec.md and plan.md to map task relationships, outputting a tasks.md file with explicit parallel execution markers and dependency-aware story ordering.

Can I use spec-kit task generation if my project lacks a .specify directory?

Spec-kit task generation requires access to the project's .specify directory and design documents, meaning projects without this structure cannot produce the dependency-aware tasks.md file.

What is the best way to break down a spec-kit plan.md into phased, testable development increments?

The best way to break down a plan.md into testable increments is to convert its content into per-user-story task phases with explicit file paths, validating checklist format and suggesting an MVP scope for incremental delivery.

Does spec-kit task generation support optional data models and contracts for user story breakdown?

Spec-kit task generation supports optional data-model or contracts documents, integrating them alongside plan.md and spec.md to produce per-user-story task phases and dependency graphs in the output tasks.md file.