speckit.tasks

Generates a dependency-ordered tasks.md checklist from feature design documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification and implementation plan into an actionable, ordered task list is tedious and error-prone. This Skill automates that step by reading your design artifacts and producing a structured tasks.md that an LLM or developer can execute directly. ## Core Features & Use Cases - Design-Aware Task Generation: Reads plan.md, spec.md, data-model.md, contracts/, research.md, and quickstart.md to derive tasks grounded in your actual design. - User-Story Organization: Groups tasks into phases by user story priority (P1, P2, P3) so each story is independently implementable and testable. - Strict Checklist Format: Every task follows a validated format with checkbox, sequential task ID, parallelization marker, story label, and exact file path. - Use Case: After writing a spec and plan for a new API feature, run this Skill to get a tasks.md with setup, foundational, per-story, and polish phases, plus a dependency graph and MVP scope suggestion. ## Quick Start Ask the agent to generate the tasks.md for the current feature based on the available design documents 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 feature specification?▼

Run the speckit.tasks workflow after creating spec.md and plan.md in your feature directory. It reads the design documents, maps entities and endpoints to user stories, and outputs a phased, dependency-ordered tasks.md.

What documents are required to generate implementation tasks?▼

Only plan.md (tech stack and structure) and spec.md (prioritized user stories) are required. data-model.md, contracts/, research.md, and quickstart.md are optional and enrich the generated tasks when present.

How are tasks organized in the generated tasks.md?▼

Tasks are grouped into phases: Setup, Foundational prerequisites, one phase per user story in priority order, and a final Polish phase. Each user story phase is independently testable with its own goal and test criteria.

Does the task generator include test tasks automatically?▼

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.

What format must each generated task follow?▼

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