speckit-tasks

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

2|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/guestgraph/engine --skill speckit-tasks-guestgraph
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/guestgraph/engine/tree/main/.claude/skills/speckit-tasks
Command: npx skills add https://github.com/guestgraph/engine --skill speckit-tasks-guestgraph

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 that step by reading spec-kit design documents and producing a structured tasks.md where every task is specific enough to execute without additional context. ## Core Features & Use Cases - Story-Organized Task Generation: Reads spec.md user stories with priorities and creates one phase per story, each independently testable. - Strict Checklist Format: Every task follows a validated format with checkbox, sequential task ID, parallelization marker, story label, and exact file path. - Extension Hook Support: Dispatches optional and mandatory pre/post hooks declared in .specify/extensions.yml before and after generation. - Use Case: After writing spec.md and plan.md for a new feature, run this Skill to get a complete tasks.md with setup, foundational, per-story, and polish phases, plus a dependency graph and MVP scope recommendation. ## 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 spec-kit specification?▼

Run the speckit-tasks skill in a project with a .specify directory. It executes setup-tasks.sh, loads spec.md and plan.md from the feature directory, and writes a tasks.md organized by user story with sequential task IDs and file paths.

What documents does spec-kit task generation require?▼

It requires plan.md for tech stack and structure, and spec.md for prioritized user stories. Optional inputs include data-model.md, contracts/, research.md, and quickstart.md, which enrich entity mapping and setup tasks when present.

Does speckit-tasks work without a .specify directory?▼

No. The skill requires the spec-kit project structure because it runs .specify/scripts/bash/setup-tasks.sh to locate the feature directory and tasks template. Without that structure, the setup step cannot resolve the required paths.

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 task uses a strict checklist format with checkbox, task ID, optional [P] parallel marker, story label, and file path.

Are test tasks always included in the generated task list?▼

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 only.