speckit-tasks

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/eovipmak/unattended-iso --skill speckit-tasks-eovipmak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/eovipmak/unattended-iso/tree/main/.commandcode/skills/speckit-tasks
Command: npx skills add https://github.com/eovipmak/unattended-iso --skill speckit-tasks-eovipmak

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 that step by reading your spec-kit design documents and producing a structured tasks.md where every task is specific enough to execute without extra 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, parallel markers, story labels, and exact file paths. - Dependency & Parallelism Mapping: Produces a dependency graph of story completion order plus parallel execution examples per story. - Extension Hooks: Supports optional and mandatory pre/post hooks declared in .specify/extensions.yml. - Use Case: After running spec-kit plan and specify steps for a new feature, invoke this Skill to get a complete tasks.md with MVP scope suggestion and per-story task counts. ## Quick Start Ask the agent 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 user stories with priorities. Optional inputs include data-model.md, contracts/, research.md, quickstart.md, and a constitution.md for governance constraints.

Does the tasks.md format support parallel execution?

Yes. Tasks that touch different files with no incomplete dependencies receive a [P] marker, and each user story phase includes parallel execution examples plus a dependency graph showing story completion order.

Are test tasks always included in 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 only implementation tasks.

What are the limitations of spec-kit task generation?

It only works inside a spec-kit project with the .specify structure and requires at least spec.md and plan.md to exist. Projects without user stories prioritized in spec.md cannot get story-organized phases.