speckit-tasks

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

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/charlesguse/wing-commander --skill speckit-tasks-charlesguse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/charlesguse/wing-commander/tree/main/.claude/skills/speckit-tasks
Command: npx skills add https://github.com/charlesguse/wing-commander --skill speckit-tasks-charlesguse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification and implementation plan into an actionable, ordered task list is manual and error-prone. This Skill automates that step by reading your spec-kit design documents and producing a structured tasks.md where every task is specific enough to execute without extra context. ## Core Features & Use Cases - Story-Organized Task Generation: Reads spec.md user stories with priorities and creates one phase per story, plus Setup, Foundational, and Polish phases. - Strict Checklist Format: Every task follows a validated format with checkbox, sequential task ID, parallel markers, story labels, and exact file paths. - Dependency & Parallelism Mapping: Produces a dependency graph of story completion order and identifies tasks that can run in parallel. - Extension Hooks: Supports optional and mandatory pre/post hooks declared in .specify/extensions.yml. - Use Case: After merging a spec and plan PR in a spec-kit project, run this Skill to generate tasks.md so implementation can begin story by story, starting with an MVP scope. ## Quick Start Ask the agent to generate the tasks.md for the current feature from the spec and plan in the feature 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 spec-kit specification?▼

Run the speckit-tasks skill in a project with a .specify directory. It executes setup-tasks.sh, loads plan.md and spec.md from the feature directory, and writes a tasks.md organized by user story with sequential task IDs and file paths.

What documents are required to generate implementation tasks?▼

plan.md and spec.md are required; they provide the tech stack and prioritized user stories. Optional documents like data-model.md, contracts/, research.md, and quickstart.md enrich the generated tasks when present.

Does the task generator include test tasks automatically?▼

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 organized by user story.

What format must generated tasks follow?▼

Every task must be a markdown checkbox with a sequential ID (T001, T002...), an optional [P] parallel marker, a story label like [US1] for user-story phases, and a description with an exact file path. Tasks missing any component are invalid.

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

Yes. Define hooks under hooks.before_tasks or hooks.after_tasks in .specify/extensions.yml. Mandatory hooks (optional: false) are executed automatically, while optional hooks are suggested with their command and prompt.