speckit-tasks

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

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/Omkar-code-mur/Job-Radar --skill speckit-tasks-omkar-code-mur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/Omkar-code-mur/Job-Radar/tree/main/Spec-it_job-Radar/.github/skills/speckit-tasks
Command: npx skills add https://github.com/Omkar-code-mur/Job-Radar --skill speckit-tasks-omkar-code-mur

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 required 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 plus parallel execution examples per story. - Extension Hooks: Supports optional and mandatory pre/post hooks configured in .specify/extensions.yml. - Use Case: After writing spec.md and plan.md for a new feature, run this Skill to get a complete tasks.md with setup, foundational, per-story, and polish phases, ready for incremental MVP-first delivery. ## 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 feature specification?

Run this Skill inside a spec-kit project after creating spec.md and plan.md. It executes the setup-tasks script, loads available design documents, and writes a tasks.md organized by user story with sequential task IDs and file paths.

What documents are required to generate implementation tasks?

Only plan.md and spec.md are required. Optional documents like data-model.md, contracts/, research.md, and quickstart.md enrich the output, and the Skill generates tasks based on whatever is available in the feature directory.

Does the tasks generator work without a .specify directory?

No. The Skill requires a spec-kit project structure with a .specify directory containing the setup-tasks PowerShell script and templates. Without it, the setup step cannot resolve the feature directory or task template.

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