speckit-tasks

Generates dependency-ordered tasks.md checklists from spec-kit design documents.

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

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 spec-kit design artifacts and producing a structured tasks.md file organized by user story. ## Core Features & Use Cases - Design Document Parsing: Loads plan.md, spec.md, data-model.md, contracts/, research.md, and quickstart.md from the feature directory to extract tech stack, user stories, and entities. - Story-Organized Task Generation: Produces phases for setup, foundational work, one phase per prioritized user story, and polish, with each task following a strict checklist format including task IDs, parallel markers, story labels, and file paths. - Extension Hook Support: Executes optional and mandatory pre/post hooks defined in .specify/extensions.yml before and after task generation. - Use Case: After writing a spec and plan for a new checkout feature, run this Skill to get a tasks.md where each user story is an independently testable phase with clear dependencies and MVP scope. ## Quick Start Ask the AI 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 the speckit-tasks workflow in a spec-kit project. It reads plan.md and spec.md from the feature directory, extracts user stories with priorities, and writes a tasks.md organized into setup, foundational, per-story, and polish phases.

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

Every task follows a strict checklist format: a markdown checkbox, sequential task ID like T001, an optional [P] parallel marker, a story label like [US1] for user story phases, and a description with an exact file path.

Does speckit-tasks require a spec-kit project structure?▼

Yes, it requires a .specify directory with the setup-tasks.ps1 script and a feature directory containing at least plan.md and spec.md. Optional documents like data-model.md, contracts/, and research.md enrich the generated tasks when present.

Are test tasks always generated in tasks.md?▼

No, test tasks are optional. They 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.

What are extension hooks in spec-kit task generation?▼

Hooks are commands defined in .specify/extensions.yml under hooks.before_tasks or hooks.after_tasks. Mandatory hooks execute automatically via EXECUTE_COMMAND, while optional hooks are presented for the user to run manually.