speckit-tasks

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

1|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/360org/vuaassistant --skill speckit-tasks-360org
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/360org/vuaassistant/tree/main/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/360org/vuaassistant --skill speckit-tasks-360org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification and implementation plan into an actionable, ordered task list is slow 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 immediately. ## Core Features & Use Cases - Story-Organized Task Generation: Reads spec.md user stories with priorities and creates one phase per story, so each increment is independently testable. - Strict Checklist Format: Every task follows a checkbox + task ID + [P] parallel marker + [US#] story label + file path format, with dependency graphs and parallel execution examples. - Extension Hooks: Supports optional and mandatory pre/post hooks declared in .specify/extensions.yml for custom workflow integration. - Use Case: After running spec-kit's specify and plan steps for a new feature, invoke this Skill to produce a tasks.md with setup, foundational, per-story, and polish phases, plus a suggested MVP scope. ## Quick Start Ask the agent to generate the tasks.md for the current feature based on the existing spec.md and plan.md in the spec-kit project.

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 the speckit-tasks skill inside a spec-kit project. It reads spec.md for user stories and plan.md for the tech stack, then writes a tasks.md organized into setup, foundational, per-story, and polish phases with sequential task IDs.

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

Every task must be a markdown checkbox with a sequential ID like T001, an optional [P] marker for parallelizable work, a [US#] story label for user-story phases, and a description ending with an exact file path.

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

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 add custom hooks before or after task generation?▼

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

When are test tasks included in the generated tasks.md?▼

Test tasks are optional and only generated when explicitly requested in the feature specification or when the user asks for a TDD approach. Otherwise the phases contain implementation tasks only.