speckit-tasks

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

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/ArMaTeC/Redball --skill speckit-tasks-armatec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/ArMaTeC/Redball/tree/main/.devin/skills/speckit-tasks
Command: npx skills add https://github.com/ArMaTeC/Redball --skill speckit-tasks-armatec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification and implementation plan into an actionable, ordered task list is tedious and error-prone. This Skill automates that step by reading your spec-kit design documents and producing a structured tasks.md organized by user story. ## Core Features & Use Cases - Automated Task Generation: Reads plan.md, spec.md, data-model.md, contracts/, and research.md to produce a complete tasks.md with sequential task IDs, parallelization markers, and file paths. - User Story Organization: Groups tasks into phases (Setup, Foundational, one phase per user story, Polish) so each story is independently implementable and testable. - Extension Hooks: Supports optional and mandatory pre/post hooks defined in .specify/extensions.yml for integrating custom commands into the workflow. - Use Case: After writing a spec and plan for a new feature, run this Skill to instantly get a checklist-format tasks.md with dependency graphs, parallel execution examples, and a suggested MVP scope. ## Quick Start Ask the agent to generate the tasks.md for the current feature based on the spec and plan in the .specify directory.

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 a feature specification?▼

Run this Skill in a spec-kit project after creating spec.md and plan.md. It executes setup_tasks.py to locate design documents, extracts user stories and tech stack, then writes a tasks.md with phases, task IDs, and file paths.

What is the task checklist format in spec-kit tasks.md?▼

Every task follows the format '- [ ] [TaskID] [P?] [Story?] Description with file path'. The [P] marker indicates parallelizable tasks, and [US1]/[US2] labels map tasks to user stories from spec.md.

Does speckit-tasks require all design documents to exist?▼

No. Only plan.md and spec.md are required. data-model.md, contracts/, research.md, and quickstart.md are optional and are incorporated when present to enrich the generated tasks.

Can I add custom hooks before or after task generation?▼

Yes. Define hooks under hooks.before_tasks or hooks.after_tasks in .specify/extensions.yml. Hooks can be optional or mandatory, and disabled hooks are skipped automatically.

Are test tasks always included in the generated tasks.md?▼

No. Test tasks are only generated when explicitly requested in the feature specification or when the user asks for a TDD approach. Otherwise the output focuses on implementation tasks.