speckit-tasks

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

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/secrakib/rag-eval-project --skill speckit-tasks-secrakib
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/secrakib/rag-eval-project/tree/main/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/secrakib/rag-eval-project --skill speckit-tasks-secrakib

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning feature specifications and design documents into an actionable, ordered implementation plan is time-consuming and error-prone. This Skill automates the creation of a structured tasks.md file so every user story becomes a set of concrete, independently testable tasks. ## 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. - Strict Checklist Format: Every task follows a validated format with checkbox, sequential task ID, parallel markers, story labels, and exact file paths. - Extension Hook Support: Executes pre- and post-generation hooks defined in .specify/extensions.yml, including mandatory hooks that must run before completion. - Use Case: After writing a feature spec and implementation plan in a spec-kit project, run this Skill to produce a tasks.md with setup, foundational, per-story, and polish phases, plus a dependency graph and MVP scope recommendation. ## Quick Start Ask the agent to generate the tasks.md for the current feature based on the spec and plan in the .specify project 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 executes setup_tasks.py, loads spec.md and plan.md from the feature directory, and produces a tasks.md organized by user story with sequential task IDs and file paths.

What documents are required to generate implementation tasks?▼

The skill requires plan.md for tech stack and structure, and spec.md for user stories with priorities. Optional documents like data-model.md, contracts/, research.md, and quickstart.md enrich the generated tasks when present.

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

No, it requires a spec-kit project structure with a .specify directory containing the setup script and templates. Without it, the setup step that resolves FEATURE_DIR and the tasks template cannot run.

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. They are only generated when explicitly requested in the feature specification or when the user asks for a TDD approach; otherwise the skill produces implementation tasks only.