speckit-tasks

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

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/zhangliuliuzhang/memcached-rvv-v2 --skill speckit-tasks-zhangliuliuzhang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/zhangliuliuzhang/memcached-rvv-v2/tree/main/.claude/skills/speckit-tasks
Command: npx skills add https://github.com/zhangliuliuzhang/memcached-rvv-v2 --skill speckit-tasks-zhangliuliuzhang

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 the creation of a tasks.md file that organizes work by user story with clear dependencies and parallelization opportunities. ## Core Features & Use Cases - Story-Organized Task Generation: Reads spec.md, plan.md, data-model.md, and contracts to produce one phase per user story in priority order. - Strict Checklist Format: Every task follows a validated format with checkbox, sequential task ID, parallel marker, story label, and exact file path. - Extension Hook Support: Executes pre- and post-generation hooks defined in .specify/extensions.yml for customizable workflows. - Use Case: After writing a spec and plan for a new feature, run this Skill to instantly get a complete tasks.md with setup, foundational, per-story, and polish phases, plus an MVP scope recommendation. ## Quick Start Ask the assistant 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 skill in a spec-kit project after creating spec.md and plan.md. It reads the design artifacts, organizes tasks by user story in priority order, and writes a formatted tasks.md with dependencies and parallel execution examples.

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

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 the story label.

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

Yes, it requires a .specify directory containing the feature's design documents. It runs .specify/scripts/powershell/setup-tasks.ps1 to locate FEATURE_DIR and the tasks template, and optionally reads .specify/memory/constitution.md for project principles.

Are test tasks always generated in tasks.md?

No, test tasks are optional. They are only generated if explicitly requested in the feature specification or if the user asks for a TDD approach. Otherwise the phases contain only implementation tasks.

How are user story dependencies handled in generated tasks?

Tasks are organized so each user story phase is independently testable, with a dependencies section showing story completion order. Foundational tasks that block all stories are placed in Phase 2 before any story phase begins.