speckit-tasks

Generate a dependency-aware tasks.md from design artifacts using .specify templates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of a dependency-aware tasks.md by transforming design artifacts into structured, executable tasks organized by the feature's user stories.

Core Features & Use Cases

  • Automated task planning: Generates a tasks.md by analyzing plan.md, spec.md, and available design artifacts in the .specify structure.
  • Dependency graph: Produces a clear execution order and parallelizable task examples per user story.
  • Extensible structure: Supports optional data-models, contracts, and decisions when present.

Quick Start

Generate the tasks.md from the repository's design artifacts using the provided .specify templates.

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

To generate a tasks.md from design artifacts, you use the .specify templates to analyze plan.md, spec.md, and available design artifacts, transforming them into an actionable execution plan.

How are tasks ordered by user stories and dependencies?

Tasks are ordered by user stories and dependencies by deriving a dependency graph from design artifacts, producing a clear execution order and parallelizable task examples per user story.

Do I need .specify templates to create a dependency-ordered task list?

Yes, you need .specify templates to create a dependency-ordered task list, as the generation process leverages these templates to structure the repository's design artifacts into a ready-to-run tasks document.

What is the best way to automate project planning from a spec.md?

The best way to automate project planning from a spec.md is to transform design artifacts into a structured tasks.md, organizing executable tasks by the feature's user stories and dependency order.

Can I include data-models, contracts, and decisions in the task planning?

Yes, you can include data-models, contracts, and decisions in the task planning, as the extensible structure supports these optional design artifacts when present in the .specify repository.

When do I need a dependency-aware tasks document for project handoffs?

You need a dependency-aware tasks document for project handoffs when you want consistent project planning, ensuring downstream execution follows a clear dependency order derived from user stories.