speckit-tasks

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

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/desarrolloainia/nuevo_circuito_mir --skill speckit-tasks-desarrolloainia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/desarrolloainia/nuevo_circuito_mir/tree/main/backend/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/desarrolloainia/nuevo_circuito_mir --skill speckit-tasks-desarrolloainia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning feature specifications and implementation plans into an actionable, ordered task list is time-consuming and error-prone. This Skill automates the creation of a tasks.md file that organizes work by user story with clear dependencies and parallelization opportunities. ## Core Features & Use Cases - Story-Organized Task Generation: Reads spec.md, plan.md, data-model.md, and contracts to produce tasks grouped by prioritized user stories (P1, P2, P3). - Strict Checklist Format: Every task follows a validated format with checkbox, sequential task ID, parallel markers, story labels, and exact file paths. - Extension Hook Support: Executes pre- and post-generation hooks defined in .specify/extensions.yml for customizable workflows. - Use Case: After writing a feature spec and implementation plan with spec-kit, run this Skill to instantly produce a tasks.md where each user story is an independently testable increment with a suggested MVP scope. ## Quick Start Ask the AI to generate the tasks.md for the current feature based on the spec and plan in the .specify project structure.

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 after creating spec.md and plan.md. It reads the design artifacts, extracts user stories with priorities, and outputs a tasks.md organized by story with dependency ordering and parallel execution examples.

What task format does spec-kit tasks.md use?▼

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

Does speckit-tasks require all design documents to exist?▼

No. Only plan.md and spec.md are required. Optional documents like data-model.md, contracts/, research.md, and quickstart.md are used when available to enrich task generation with entities, contracts, and decisions.

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 only implementation tasks are produced.

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 execute automatically before or after generation, while optional hooks are suggested to the user for manual execution.