speckit-tasks

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

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

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 documents 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 Hooks: Supports optional and mandatory pre/post hooks declared in .specify/extensions.yml for integrating custom commands into the workflow. - Use Case: After running spec-kit's specify and plan steps for a new feature, invoke this Skill to generate a tasks.md with dependency graphs, parallel execution examples, and 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 this Skill inside a spec-kit project after creating spec.md and plan.md. It reads the design documents 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, quickstart.md, and a constitution.md for governance constraints.

Does this Skill work without a .specify directory?▼

No. It depends on the spec-kit project structure, including .specify/scripts/setup-tasks.sh and the tasks template. Without that structure, the setup step cannot resolve FEATURE_DIR or the template path.

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