speckit-tasks

Convert design artifacts into a dependency-ordered tasks.md with user stories.

57|13|Updated Jul 12, 2025
One-click install
npx skills add https://github.com/heidsoft/itsm --skill speckit-tasks-heidsoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/heidsoft/itsm/tree/main/.claude/skills/speckit-tasks
Command: npx skills add https://github.com/heidsoft/itsm --skill speckit-tasks-heidsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates turning design artifacts into a structured, dependency-aware tasks.md to guide feature implementation.

Core Features & Use Cases

  • Generate a tasks.md organized by user stories (US1, US2, etc.) from plan.md, spec.md, and related artifacts.
  • Build a dependency graph and parallelization hints to optimize execution order.
  • Produce a completion report and ensure every task follows a strict checklist format for easy execution.

Quick Start

Run the speckit-tasks skill from the project root to generate a tasks.md based on available design artifacts.

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 list from design artifacts?

You can generate a dependency-ordered task list by converting existing design artifacts like plan.md and spec.md into a structured tasks.md grouped by user stories with parallelization cues.

What design documents do I need to create a tasks.md for feature implementation?

You need design artifacts such as plan.md, spec.md, data-model.md, contracts/, and research/ documents to generate a structured tasks.md for feature implementation.

Can I use this to organize tasks by user stories and build a dependency graph?

Yes, this skill organizes tasks by user stories (US1, US2) and builds a dependency graph to optimize execution order for feature implementation.

What's the best way to automate turning architecture specs into an MVP-focused output?

The best way to automate turning architecture specs into an MVP-focused output is using a skill that parses design documents to produce a strict checklist format with a completion summary.

Do I need to manually add file paths to the generated user stories?

No, the generated tasks automatically reference file paths and follow a strict checklist format, ensuring easy execution without manual path entry.