speckit-tasks

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

4|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/sethdavis512/iridium --skill speckit-tasks-sethdavis512
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/sethdavis512/iridium/tree/main/.claude/skills/speckit-tasks
Command: npx skills add https://github.com/sethdavis512/iridium --skill speckit-tasks-sethdavis512

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 your spec-kit design artifacts and producing a structured tasks.md that an LLM or developer can execute directly. ## Core Features & Use Cases - Design-driven task generation: Reads plan.md, spec.md, and optional artifacts (data-model.md, contracts/, research.md, quickstart.md) to derive tasks grounded in your actual design. - User-story organization: Groups tasks into phases per user story (P1, P2, P3...) with dependency graphs, parallel execution markers, and independent test criteria. - Strict checklist format: Enforces a consistent task format (checkbox, task ID, [P] parallel marker, [USn] story label, file paths) so output is immediately executable. - Extension hooks: Supports optional and mandatory before/after hooks declared in .specify/extensions.yml. - Use Case: After writing a spec and plan for a new feature, run this Skill to get a tasks.md with setup, foundational, per-story, and polish phases, plus a suggested MVP scope. ## 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. It reads plan.md and spec.md from the feature directory, maps entities and contracts to user stories, and writes a dependency-ordered tasks.md following a strict checklist format.

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 documents like data-model.md, contracts/, research.md, and quickstart.md 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 task has an ID, optional [P] parallel marker, [USn] story label, and exact file path.

Does the task generator work without a .specify directory?▼

No. The skill requires a spec-kit project structure with a .specify directory containing the setup script, templates, and feature design documents. Without it, the setup step cannot resolve FEATURE_DIR or the tasks template.

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. Implementation tasks are always generated per user story.