speckit-tasks

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

5|1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/theonlytruebigmac/n-central-rest-api-mcp --skill speckit-tasks-theonlytruebigmac
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/theonlytruebigmac/n-central-rest-api-mcp/tree/main/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/theonlytruebigmac/n-central-rest-api-mcp --skill speckit-tasks-theonlytruebigmac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification and implementation plan into an actionable, ordered task list is tedious 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, 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 identifies tasks that can run in parallel. - Extension Hooks: Supports optional and mandatory pre/post hooks declared in .specify/extensions.yml. - Use Case: After running spec-kit's specify and plan steps for a new feature, invoke this Skill to generate a tasks.md that an LLM or developer can execute incrementally, starting with an MVP scope of just User Story 1. ## Quick Start Ask the agent to generate the tasks.md for the current feature based on the spec.md and plan.md in the spec-kit feature 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 spec-kit feature specification?▼

Run the speckit-tasks skill in a project with a .specify directory. It executes setup-tasks.sh, loads spec.md and plan.md 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, and quickstart.md, which enrich entity mapping and setup tasks when present.

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

No. The skill requires a spec-kit project structure with a .specify directory containing the setup-tasks.sh script and feature artifacts. Without it, the setup step cannot resolve FEATURE_DIR or the tasks template.

Are test tasks always included in the generated tasks.md?▼

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.

What format must each generated task follow?▼

Each task must be a markdown checkbox with a sequential ID like T001, an optional [P] parallel marker, a story label like [US1] for story-phase tasks, and a description ending with an exact file path.