speckit-tasks

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

9|2|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/opsmill/infrahub-solution-ai-dc --skill speckit-tasks-opsmill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/opsmill/infrahub-solution-ai-dc/tree/main/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/opsmill/infrahub-solution-ai-dc --skill speckit-tasks-opsmill

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 artifacts and producing a structured tasks.md organized by user story. ## 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, 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: Executes optional and mandatory pre/post hooks defined in .specify/extensions.yml before and after task generation. - Use Case: After running spec-kit's specify and plan steps for a new feature, invoke this Skill to generate a complete tasks.md with dependency graph, parallel execution examples, and a suggested MVP scope. ## Quick Start Ask the agent to generate the tasks.md for the current feature based on the existing spec and plan documents.

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 this Skill in a spec-kit project after creating spec.md and plan.md. It reads the design artifacts from the feature directory and generates a tasks.md organized by user story with sequential task IDs and file paths.

What project structure does spec-kit task generation require?▼

It requires a spec-kit project with a .specify directory containing scripts and templates, plus a feature directory holding spec.md and plan.md. Optional documents like data-model.md, contracts, and research.md enrich the generated tasks.

Does the task generator include test tasks automatically?▼

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 only implementation tasks are produced.

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.

What are extension hooks in spec-kit task generation?▼

Hooks are commands defined in .specify/extensions.yml under before_tasks or after_tasks keys. Mandatory hooks are executed automatically by the Skill, while optional hooks are presented to the user for manual invocation.