speckit-tasks

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

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/speeddesigns/cvusd-calendars --skill speckit-tasks-speeddesigns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/speeddesigns/cvusd-calendars/tree/main/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/speeddesigns/cvusd-calendars --skill speckit-tasks-speeddesigns

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 the conversion of spec-kit design artifacts into a structured tasks.md file. ## Core Features & Use Cases - Design Document Parsing: Reads plan.md, spec.md, data-model.md, contracts/, and research.md from a spec-kit feature directory to extract tech stack, user stories, and priorities. - Story-Organized Task Generation: Produces phases for setup, foundational work, one phase per user story in priority order, and polish, with strict checklist formatting (checkbox, task ID, [P] parallel markers, [USn] story labels, file paths). - Extension Hook Support: Executes optional and mandatory before/after hooks declared in .specify/extensions.yml during task generation. - Use Case: After writing a spec and plan for a new feature, run this Skill to get a tasks.md where each user story is an independently testable increment with a suggested MVP scope. ## Quick Start Ask the agent to generate the tasks.md for the current feature using the spec and plan in the spec-kit 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 after creating spec.md and plan.md in your feature directory. It runs setup-tasks.ps1 to locate the feature, loads available design documents, and writes a tasks.md organized by user story with dependency ordering.

What documents are required to generate tasks with spec-kit?

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

What format do generated spec-kit tasks follow?

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

Does speckit-tasks work without a .specify directory?

No. The Skill requires a spec-kit project structure with a .specify directory containing scripts like setup-tasks.ps1 and templates. Without it, the setup step cannot resolve FEATURE_DIR or the tasks template.

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

No. Test tasks are optional and only generated when explicitly requested in the feature specification or when the user asks for a TDD approach. Otherwise phases contain models, services, endpoints, and integration tasks.