speckit-tasks

Generate phased task lists and dependency graphs from spec-style design documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts scattered design artifacts into a single, actionable tasks.md so teams and LLMs can execute feature work without ambiguous or missing steps. It removes manual translation from specifications, data models, and contracts into developer-ready tasks and dependency orders.

Core Features & Use Cases

  • Parse spec-kit style project artifacts (plan.md, spec.md, optional data-model.md, contracts, research) and extract user stories with priorities.
  • Generate a phased tasks.md with Setup, Foundational, per-user-story phases, polish phase, and a dependency graph that preserves execution order and parallel opportunities.
  • Surface extension hooks (before_tasks and after_tasks), validate checklist format, and produce an execution report summarizing task counts, per-story tests, and suggested MVP scope.
  • Use Case: A product manager or engineering lead wants an immediately runnable, checklist-style task plan for a new feature so engineers or an LLM can implement and test each story independently.

Quick Start

Run the speckit-tasks workflow on the repository root to generate an executable tasks.md for the target feature.

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 tasks.md from project design artifacts?

To generate a dependency-ordered tasks.md, apply this workflow to a spec-kit style project containing a .specify directory. It parses plan.md, spec.md, and contracts to produce a phased, checklist-style task plan with parallel execution examples.

What is the best way to convert spec-kit style specifications into actionable user story tasks?

Converting spec-kit specifications into actionable user story tasks requires parsing design artifacts like spec.md and data-model.md. This process extracts user stories with priorities and outputs an executable checklist format organized by implementation phases.

Can I use this task generation process if my project lacks a data-model.md file?

You can use this task generation process without a data-model.md file because it is an optional input artifact. The workflow primarily requires a .specify directory containing plan.md and spec.md to successfully extract user stories and generate the dependency graph.

How does the generated tasks.md handle parallel execution and extension hooks?

The generated tasks.md handles parallel execution by mapping a dependency graph that preserves execution order and identifies parallel opportunities. It also surfaces before_tasks and after_tasks extension hook notices to allow custom workflow integration.

What does the execution report include when generating tasks from a feature plan?

The execution report summarizes task generation results by including total task counts, per-story test mappings, and a suggested MVP scope. This provides engineering teams with a clear overview of the implementation requirements extracted from the design artifacts.