speckit-tasks

Generates dependency-ordered tasks.md checklists from spec-kit design documents.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/msaid1976/TSP-SmartAIRoute --skill speckit-tasks-msaid1976
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/msaid1976/TSP-SmartAIRoute/tree/main/SmartRouteAI/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/msaid1976/TSP-SmartAIRoute --skill speckit-tasks-msaid1976

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 spec-kit design artifacts and producing a structured tasks.md file where every task is specific enough to execute immediately. ## Core Features & Use Cases - Design Document Ingestion: Reads plan.md, spec.md, and optional data-model.md, contracts/, research.md, and quickstart.md from the feature directory. - Story-Organized Task Generation: Creates phases per user story in priority order, with setup, foundational, and polish phases, plus dependency graphs and parallel execution examples. - Strict Checklist Format: Enforces a consistent task format with checkboxes, sequential task IDs, [P] parallel markers, [US#] story labels, and exact file paths. - Use Case: After writing a spec and plan for a new API feature, run this Skill to produce a tasks.md where each user story is an independently testable increment, ready for LLM-assisted implementation. ## 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 file 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 are required for spec-kit task generation?▼

plan.md and spec.md are required, since they provide the tech stack and prioritized user stories. data-model.md, contracts/, research.md, and quickstart.md are optional and are used only when present.

Does this Skill work without a .specify directory?▼

No. It depends on the spec-kit project structure, including .specify/scripts/check-prerequisites.sh and .specify/templates/tasks-template.md. Projects without that layout cannot use it.

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 follows 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 are only generated when explicitly requested in the feature specification or when the user asks for a TDD approach.