speckit-tasks

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

1|Updated Nov 21, 2020
One-click install
npx skills add https://github.com/LuanDopke/persefone --skill speckit-tasks-luandopke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/LuanDopke/persefone/tree/main/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/LuanDopke/persefone --skill speckit-tasks-luandopke

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 documents and producing a structured tasks.md where every task is specific enough to execute without extra context. ## Core Features & Use Cases - Design-Artifact-Driven Generation: Reads plan.md, spec.md, data-model.md, contracts/, research.md, and quickstart.md from the feature directory to build tasks grounded in actual project decisions. - User-Story-Organized Phases: Creates Setup, Foundational, per-user-story (P1, P2, P3...), and Polish phases so each story is independently implementable and testable. - Strict Checklist Format: Enforces the - [ ] [TaskID] [P?] [Story?] Description with file path format, plus dependency graphs, parallel execution examples, and MVP scope suggestions. - Extension Hooks: Supports optional and mandatory before/after 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 produce a tasks.md with sequential task IDs, story labels, and exact file paths ready for incremental delivery. ## Quick Start Ask the agent to generate the tasks.md for the current feature using the available spec-kit design documents.

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 inside a spec-kit project. It executes setup-tasks.sh, loads plan.md and spec.md from the feature directory, and writes a tasks.md organized by user story phases with sequential task IDs and file paths.

What documents are required to generate implementation tasks?▼

plan.md and spec.md are required for tech stack and prioritized user stories. Optional documents like data-model.md, contracts/, research.md, and quickstart.md enrich the output, and tasks are generated based on whatever is available.

Does the tasks generator work without a .specify directory?▼

No. The skill requires a spec-kit project structure with a .specify/ directory, since it runs .specify/scripts/bash/setup-tasks.sh and falls back to .specify/templates/tasks-template.md for the output structure.

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 follows the format `- [ ] [TaskID] [P?] [Story?] Description with 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.