speckit-tasks

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

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/NarenKarthikBM/specseyal --skill speckit-tasks-narenkarthikbm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/NarenKarthikBM/specseyal/tree/main/.claude/skills/speckit-tasks
Command: npx skills add https://github.com/NarenKarthikBM/specseyal --skill speckit-tasks-narenkarthikbm

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 in a spec-driven development workflow by reading your design artifacts 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, plus setup, foundational, and polish phases. - Strict Checklist Format: Every task follows a validated format with checkbox, sequential task ID, parallelization marker, story label, and exact file path. - Dependency & Parallelism Mapping: Produces a dependency graph of story completion order and marks tasks that can run in parallel. - Extension Hooks: Supports configurable before/after hooks via .specify/extensions.yml, with mandatory hooks executed and blocking on failure. - Use Case: After running spec-kit's plan phase for a new feature, invoke this Skill to generate tasks.md with an MVP scope suggestion, per-story task counts, and independent test criteria for each user story. ## Quick Start Ask the assistant to generate the tasks.md for the current feature from the existing spec.md and plan.md, optionally noting any task generation constraints.

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 inside a spec-kit project after the plan phase. It reads spec.md user stories and plan.md tech stack, then writes a tasks.md organized into setup, foundational, per-story, and polish phases with sequential task IDs and file paths.

How are tasks organized by user story in spec-driven development?

Each user story from spec.md gets its own phase in priority order (P1, P2, P3), containing the models, services, and endpoints that story needs. Tasks carry a story label like [US1], and each phase is an independently testable increment.

Does speckit-tasks require a specific project structure?

Yes, it requires a spec-kit initialized project with a .specify directory containing scripts and templates. It reads plan.md and spec.md from the feature directory and falls back to .specify/templates/tasks-template.md if no template path is returned.

Are test tasks generated automatically in tasks.md?

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 phases contain implementation tasks only.

What happens when a before_tasks extension hook fails?

A non-zero exit from a mandatory before_tasks hook is a hard block and task generation stops. The hook issue, such as a stale gate approval, must be resolved before retrying; it is never treated as advisory.