speckit-tasks

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

Updated Sep 19, 2026
One-click install
npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill speckit-tasks-ab0umar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/Ab0umar/selrs.cc.BU/tree/main/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill speckit-tasks-ab0umar

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 file organized by user story. ## Core Features & Use Cases - Design Artifact Parsing: Reads plan.md, spec.md, data-model.md, contracts/, research.md, and quickstart.md from the feature directory to extract tech stack, user stories, and entities. - Story-Organized Task Generation: Produces phases for setup, foundational work, one phase per user story in priority order, and a final polish phase, with each task following a strict checklist format (checkbox, task ID, [P] parallel marker, [US#] story label, file path). - Extension Hook Support: Checks .specify/extensions.yml for before_tasks and after_tasks hooks and executes or surfaces them as slash commands. - Use Case: After running spec-kit's specify and plan commands for a new feature, invoke this Skill to generate a tasks.md where each user story is an independently testable increment with dependency graphs and parallel execution examples. ## Quick Start Generate the tasks.md for the current feature from my spec.md and plan.md, organized by user story with parallel execution markers.

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 feature specification?▼

Run this Skill in a spec-kit project after creating spec.md and plan.md. It reads the design artifacts from the feature directory and writes a tasks.md organized by user story, with setup, foundational, 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] marker for parallelizable tasks, a [US#] story label for user story phases, and a description with an exact file path.

Does task generation require all spec-kit documents to exist?▼

No. Only plan.md and spec.md are required. data-model.md, contracts/, research.md, and quickstart.md are optional, and tasks are generated based on whichever documents are available in the feature directory.

Are test tasks always included in the generated 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 models, services, endpoints, and integration tasks.

What are spec-kit extension hooks in task generation?▼

Hooks are entries under hooks.before_tasks or hooks.after_tasks in .specify/extensions.yml. The Skill checks them before and after generation, executing mandatory hooks as slash commands and surfacing optional ones for the user to run.