speckit-tasks

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

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/dantasgut/clayflow --skill speckit-tasks-dantasgut
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/dantasgut/clayflow/tree/main/.claude/skills/speckit-tasks
Command: npx skills add https://github.com/dantasgut/clayflow --skill speckit-tasks-dantasgut

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of a dependency-ordered tasks.md from design artifacts (plan.md, spec.md, data-model.md, contracts/, research.md) to accelerate feature delivery.

Core Features & Use Cases

  • Generates Phase-based tasks organized by user stories (US1, US2, etc.) with clear file paths and dependencies
  • Supports optional sources such as data-model.md and contracts/ to map entities and interfaces to tasks
  • Outputs a finished tasks.md that follows a strict checklist format and includes parallelization opportunities and MVP guidance

Quick Start

Analyze the repository design artifacts and request a complete tasks.md for the 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 feature design artifacts?

To generate a dependency-ordered tasks.md from feature design artifacts, you analyze your repository's plan.md and spec.md files. The tool processes these spec-driven inputs to output a structured checklist organized by user stories and phases.

What is a spec-driven workflow for organizing development tasks by user stories?

A spec-driven workflow organizes development tasks by analyzing design documents like spec.md and plan.md to map entities and interfaces. It produces structured task phases grouped by user stories with clear file paths and dependencies.

Does task generation work with optional artifacts like data-model.md and contracts?

Yes, task generation works with optional artifacts like data-model.md and contracts/ directories. Mapping these interface and entity definitions ensures the resulting checklist accurately reflects the technical dependencies of your feature.

Can I add custom hooks before or after task generation from spec files?

Yes, you can add custom hooks before or after task generation from spec files. The generation process supports extension hooks, allowing you to inject custom logic into the workflow that builds your dependency-ordered checklist.

What's the best way to parallelize development tasks mapped from a spec.md file?

The best way to parallelize development tasks mapped from a spec.md file is to use a generated checklist that explicitly identifies parallelization opportunities. This output also includes MVP guidance to help prioritize the execution order.

Why does my generated tasks checklist need a strict format for spec-driven projects?

Your generated tasks checklist needs a strict format for spec-driven projects to ensure automated tracking and clear dependency resolution. The output follows a strict checklist format with per-story task grouping to maintain structural consistency.