speckit-tasks

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

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Argoss84/Kando-Caracter-sheet-generator --skill speckit-tasks-argoss84
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/Argoss84/Kando-Caracter-sheet-generator/tree/main/.cursor/skills/speckit-tasks
Command: npx skills add https://github.com/Argoss84/Kando-Caracter-sheet-generator --skill speckit-tasks-argoss84

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 the creation of a tasks.md file that organizes work by user story so each increment is independently implementable and testable. ## Core Features & Use Cases - Story-Organized Task Generation: Reads spec.md, plan.md, data-model.md, and contracts to produce phases per user story with strict checklist formatting (checkbox, task ID, [P] markers, [US] labels, file paths). - Dependency & Parallelism Analysis: Produces a dependency graph of story completion order plus parallel execution examples per story. - Extension Hook Support: Executes pre- and post-generation hooks defined in .specify/extensions.yml, handling optional and mandatory hooks. - Use Case: After writing a spec and plan for a new API feature, run this Skill to get a complete tasks.md with setup, foundational, per-story, and polish phases, ready for an LLM or developer to execute task by task. ## Quick Start Ask the agent to generate the tasks.md for the current feature based on the spec and plan in the 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 feature specification?▼

Run the speckit-tasks skill in a spec-kit project. It executes setup-tasks.ps1 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 task format does spec-kit tasks.md require?▼

Every task must follow the checklist format: a markdown checkbox, sequential task ID like T001, an optional [P] parallel marker, a [US1] story label for user story phases, and a description with an exact file path.

Does speckit-tasks work without a data model or contracts?▼

Yes. Only plan.md and spec.md are required. data-model.md, contracts, research.md, and quickstart.md are optional inputs that enrich task generation when present in the feature directory.

Are test tasks always generated in 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 are extension hooks in spec-kit task generation?▼

Hooks are commands defined in .specify/extensions.yml under hooks.before_tasks or hooks.after_tasks. Mandatory hooks are executed automatically before or after generation, while optional hooks are only suggested to the user.