speckit-tasks

Generate executable tasks.md files from design artifacts with dependency-ordered task plans.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-tasks automates the generation of a single, executable tasks.md by analyzing design artifacts such as the .specify/ directory to produce a dependency-ordered task plan that can be immediately acted on.

Core Features & Use Cases

  • Generates a tasks.md organized by user stories with a phased structure (Setup, Foundational, US stories, and Polish) to support incremental delivery.
  • Maps plan.md, spec.md, and optional data/contract artifacts to concrete tasks with explicit dependencies, parallelism, and MVP scope.
  • Ensures all generated tasks follow a strict checklist format, including file paths and proper story labeling where applicable.

Quick Start

Run speckit-tasks in the repository root to generate a ready-to-run tasks.md from the existing 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 auto-generate a task plan from design artifacts in my repository?

To auto-generate a task plan, run speckit-tasks in your repository root to analyze design artifacts like the .specify/ directory and produce a single, executable tasks.md organized by user stories and dependencies.

How does dependency-ordered task generation work for software features?

Dependency-ordered task generation works by analyzing your plan.md, spec.md, and optional data/contract artifacts to map concrete tasks with explicit dependencies, parallelism, and MVP scope into a phased checklist structure.

How do I structure user stories into a phased checklist for incremental delivery?

You can structure user stories into a phased checklist by generating a tasks.md that organizes work into Setup, Foundational, US stories, and Polish phases, ensuring proper story labeling and incremental delivery.

Can I generate an MVP scope task list from spec.md and data contracts?

Yes, you can generate an MVP scope task list by mapping spec.md and optional data/contract artifacts to concrete tasks that highlight parallelism and explicit dependencies for MVP planning.

Does speckit-tasks require a specific directory structure to generate a tasks.md file?

Speckit-tasks requires existing design artifacts such as the .specify/ directory, including plan.md and spec.md files, to analyze and produce a dependency-ordered tasks.md file.

What is the best way to ensure generated tasks follow a strict checklist format with file paths?

The best way to ensure a strict checklist format with file paths is to auto-generate tasks.md using speckit-tasks, which enforces checklist formatting, captures dependencies, and includes proper story labeling automatically.