speckit-tasks

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

1|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/tjsasakifln/extra-cli --skill speckit-tasks-tjsasakifln
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/tjsasakifln/extra-cli/tree/main/.grok/skills/speckit-tasks
Command: npx skills add https://github.com/tjsasakifln/extra-cli --skill speckit-tasks-tjsasakifln

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, parallel markers, story labels, and exact file paths. - 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 commands 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 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 spec-kit specification?▼

Run the speckit-tasks skill in a project with a .specify directory. It executes setup-tasks.sh to locate the feature directory, loads spec.md and plan.md, and writes a tasks.md organized by user story phases 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, quickstart.md, and .specify/memory/constitution.md for governance constraints.

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 templates. Without it, the setup step that resolves FEATURE_DIR and TASKS_TEMPLATE cannot run.

How are tasks organized in the generated tasks.md?▼

Tasks are grouped into phases: Setup, Foundational, 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 like [US1], and an exact 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.