speckit-tasks

Convert spec-kit design artifacts into a dependency-ordered tasks.md.

1|Updated Oct 21, 2025

Search Tags:#planning #tasks #speckit #spec-kit #task-generation

Ready to run

npx skills add https://github.com/code-dot-org/marketing-sites --skill speckit-tasks-code-dot-org

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/code-dot-org/marketing-sites/tree/main/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/code-dot-org/marketing-sites --skill speckit-tasks-code-dot-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating a concrete, dependency-ordered tasks.md from feature designs and spec-kit artifacts to streamline implementation planning.

Core Features & Use Cases

Convert plan.md, spec.md, and related documents into a phase-driven task list with clear file paths.
Produce user-story-aligned tasks with dependency order, parallelization notes, and a final polish phase.
Output an immediately executable tasks.md that an AI can follow to implement the feature.

Quick Start

Run speckit-tasks on your repository to generate a tasks.md from the current 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 tasks.md from spec-kit design artifacts?▼

To generate a dependency-ordered tasks.md from spec-kit design artifacts, apply this Skill to a repository containing a .specify/ directory and design documents. It converts plan.md and spec.md files into phase-driven, user-story-aligned tasks with clear file paths.

How does converting design documents into phase-based tasks work for AI implementation?▼

Converting design documents into phase-based tasks works by reading feature specs and producing a checklist-format tasks.md organized by user stories. This output includes dependency ordering, parallelization notes, and a final polish phase, creating an immediately executable plan for AI implementation.

Do I need a .specify/ directory to generate user-story-aligned tasks with dependency order?▼

Yes, you need a .specify/ directory to generate user-story-aligned tasks with dependency order. This Skill is designed to apply specifically to spec-kit projects that include this directory structure alongside related design documents to produce properly formatted, executable task lists.

Can I use this task generation process for projects without existing spec-kit artifacts?▼

No, you cannot use this task generation process for projects without existing spec-kit artifacts. The Skill requires existing design documents like spec.md and plan.md within a .specify/ directory to map features into concrete, phase-based tasks with extension hooks.

What's the best way to structure task lists for parallelization and implementation phases?▼

The best way to structure task lists for parallelization and implementation phases is to organize tasks by user stories with clear dependency order. This Skill outputs a strict checklist format that includes parallelization notes and a final polish phase for an executable plan.

What limitations exist when converting feature designs into executable tasks.md files?▼

Limitations when converting feature designs into executable tasks.md files include strict adherence to spec-kit project structures. The Skill only processes repositories with a .specify/ directory and respects extension hooks, meaning non-spec-kit design formats are not supported.