speckit-tasks

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

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/AhmedRagabRG/academy --skill speckit-tasks-ahmedragabrg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/AhmedRagabRG/academy/tree/main/frontend/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/AhmedRagabRG/academy --skill speckit-tasks-ahmedragabrg

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 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 phases per user story in priority order. - Strict Checklist Format: Every task follows a validated format with checkbox, task ID, parallel marker, story label, and exact file path. - Extension Hook Support: Executes pre- and post-generation hooks defined in .specify/extensions.yml for customizable workflows. - Use Case: After writing a spec and implementation plan for a new feature, run this Skill to instantly get a tasks.md with setup, foundational, per-story, and polish phases, plus an MVP scope recommendation. ## Quick Start Ask the agent to generate the tasks.md for the current feature based on the existing spec and plan 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 feature specification?▼

Run the speckit-tasks skill in a spec-kit project after creating spec.md and plan.md. It reads the design artifacts, organizes tasks by user story in priority order, and writes a tasks.md with setup, foundational, story, and polish phases.

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

Every task follows a strict checklist format: a markdown checkbox, sequential task ID like T001, an optional [P] parallel marker, a story label like [US1] for 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 present, and tasks are generated based on whatever is available.

Can I add custom hooks before or after task generation?▼

Yes. Define hooks under hooks.before_tasks or hooks.after_tasks in .specify/extensions.yml. Hooks can be optional or mandatory, and disabled hooks or those with conditions are skipped by the skill.

When are test tasks included in the generated tasks.md?▼

Test tasks are only generated when explicitly requested in the feature specification or when the user asks for a TDD approach. By default, tests are optional and omitted from the task list.