speckit.tasks

Convert plan.md and spec.md into a dependency-ordered tasks.md.

63|13|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/compnew2006/Spec-Kit-Antigravity-Skills --skill speckit-tasks-compnew2006
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit.tasks
Source: https://github.com/compnew2006/Spec-Kit-Antigravity-Skills/tree/main/skills/speckit.tasks
Command: npx skills add https://github.com/compnew2006/Spec-Kit-Antigravity-Skills --skill speckit-tasks-compnew2006

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to translate feature design artifacts (plan.md, spec.md, data-model.md, contracts) into a concrete, executable task list that can be tracked and delivered. This Skill automates the generation of a dependency-ordered tasks.md that aligns work with the project plan and user stories.

Core Features & Use Cases

  • Generate a complete tasks.md by ingesting plan.md, spec.md, data-model.md, and contracts/.
  • Structure work into Phase 1 Setup, Phase 2 Foundational, and Phase 3+ User Story phases in priority order, with a final Polish phase.
  • Provide a clear summary including total task count, per-story task counts, and parallelization opportunities to guide planning and execution.

Quick Start

Provide plan.md and spec.md to the task generator to produce 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 task list from plan.md and spec.md files?

To generate a dependency-ordered task list from plan.md and spec.md files, use an automation tool to ingest your feature design artifacts and output a structured tasks.md file ready for execution.

What is the best way to convert feature design artifacts into an executable task sequence?

The best way to convert feature design artifacts into an executable task sequence is to automate the parsing of plan.md, spec.md, data-model.md, and contracts/ to produce an MVP-focused tasks.md with clear phase structures.

How does task generation structure work for user stories in an MVP-focused plan?

Task generation structures work for user stories by organizing tasks into Setup, Foundational, and User Story phases in priority order, concluding with a Polish phase to align work with the project plan.

Do I need data-model.md and contracts/ to generate a tasks.md file?

You do not strictly need data-model.md and contracts/ to generate a tasks.md file; providing plan.md and spec.md as input is required, while additional artifacts enhance the MVP-focused task structure.

Can I see parallelization opportunities and per-story task counts when creating a tasks.md?

You can see parallelization opportunities and per-story task counts when creating a tasks.md by generating a concise summary that includes the total task count, per-story counts, and dependency mapping.

Why does my generated tasks.md organize work into Setup, Foundational, and User Story phases?

Your generated tasks.md organizes work into Setup, Foundational, and User Story phases to ensure dependency-ordered execution, aligning foundational architecture tasks before user story implementation and final polish.