speckit-tasks

Generate a dependency-ordered tasks.md from spec-kit design artifacts.

1|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/stefaniuk/loadout --skill speckit-tasks-stefaniuk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/stefaniuk/loadout/tree/main/.github/skills/speckit-tasks
Command: npx skills add https://github.com/stefaniuk/loadout --skill speckit-tasks-stefaniuk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved implementation plan and specification into an actionable, dependency-ordered task list is error-prone and inconsistent when done by hand. This Skill automates the generation of a structured tasks.md file so every user story maps to concrete, independently testable tasks. ## Core Features & Use Cases - Task Generation from Design Artifacts: Reads plan.md, spec.md, data-model.md, contracts/, and research.md to produce tasks organized by user story priority. - Strict Checklist Format: Enforces a consistent task format with checkboxes, sequential task IDs, parallelization markers, story labels, and exact file paths. - Extension Hooks: Supports pre- and post-generation hooks defined in .specify/extensions.yml for customizable workflow integration. - Use Case: After finishing a feature plan with spec-kit, run this Skill to produce a tasks.md where each user story phase includes Show & Tell verification steps, dependency graphs, and parallel execution examples ready for the implementation phase. ## Quick Start Ask the assistant to generate the tasks.md for the current feature using the speckit-tasks skill after the plan and spec are approved.

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 file from a spec-kit plan?▼

Run the speckit-tasks skill after your plan.md and spec.md are approved. It executes setup_tasks.py, loads available design documents from the feature directory, and outputs a tasks.md organized by user story with dependency ordering.

What task format does spec-kit tasks.md require?▼

Every task must follow the format: checkbox, sequential task ID (T001, T002), optional [P] parallel marker, story label like [US1] for user story phases, and a description with an exact file path. Setup, foundational, and polish phases omit story labels.

Does speckit-tasks work without a data model or contracts?▼

Yes, only plan.md and spec.md are required. Optional documents like data-model.md, contracts/, research.md, and quickstart.md are loaded when present and mapped to the relevant user stories.

Can I use speckit-tasks with the Superpowers workflow mode?▼

No, the skill enforces a workflow mode guard. If the active mode is superpowers, it stops and instructs you to switch with make workflow-use mode=speckit before proceeding.

When should I not use speckit-tasks for a feature?▼

For narrow repository-internal changes like make targets, scripts, docs, or patch maintenance, keep the task structure deliberately small. Do not invent extra phases or user stories to mimic a larger application workflow.