speckit-tasks

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

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/acarmonag/fullstack-devops-agent-aws-terraform --skill speckit-tasks-acarmonag
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/acarmonag/fullstack-devops-agent-aws-terraform/tree/main/codebase/rdicidr-0.1.0/.claude/skills/speckit-tasks
Command: npx skills add https://github.com/acarmonag/fullstack-devops-agent-aws-terraform --skill speckit-tasks-acarmonag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning feature specifications and design documents into an actionable, ordered implementation plan is time-consuming and error-prone. This Skill automates the creation of a tasks.md file that breaks a feature into phases and user-story-organized tasks with clear file paths and dependencies. ## Core Features & Use Cases - Automated Task Generation: Reads plan.md, spec.md, data-model.md, contracts, and research notes from a spec-kit project to produce a structured tasks.md. - User Story Organization: Groups tasks by prioritized user stories (P1, P2, P3) so each story is independently implementable and testable. - Dependency & Parallelism Mapping: Produces a dependency graph, parallel execution markers, and an MVP-first implementation strategy. - Extension Hooks: Supports pre- and post-execution hooks defined in .specify/extensions.yml for custom workflow integration. - Use Case: After writing a feature spec and implementation plan with spec-kit, run this Skill to instantly get a complete, checklist-formatted tasks.md ready for LLM-driven or manual execution. ## Quick Start Ask the AI to generate the tasks.md for the current feature based on the spec and plan in the .specify 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 after creating spec.md and plan.md. It reads the design artifacts, organizes tasks by user story priority, and writes a checklist-formatted tasks.md with task IDs, file paths, and dependencies.

What documents are required to generate implementation tasks?▼

The Skill requires plan.md for tech stack and structure, and spec.md for prioritized user stories. Optional documents like data-model.md, contracts/, research.md, and quickstart.md enrich the generated tasks when present.

Does speckit-tasks work without a .specify directory?▼

No, it requires a spec-kit project structure with a .specify directory containing the setup script and feature artifacts. Without this structure, the setup step that locates FEATURE_DIR and the tasks template cannot run.

How are tasks organized in the generated tasks.md?▼

Tasks are organized into phases: Setup, Foundational prerequisites, one phase per user story in priority order, and a final Polish phase. Each task follows a strict checklist format with checkbox, task ID, optional parallel marker, story label, and file path.

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 unmet conditions are skipped.

Are test tasks always included in the generated tasks.md?▼

No, test tasks are optional. They are only generated when explicitly requested in the feature specification or when the user asks for a TDD approach.