speckit-implement

Execute Speckit tasks from tasks.md and plan.md with phase sequencing.

Updated May 28, 2026
One-click install
npx skills add https://github.com/bdunnette/reaper --skill speckit-implement-bdunnette
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-implement
Source: https://github.com/bdunnette/reaper/tree/main/.agents/skills/speckit-implement
Command: npx skills add https://github.com/bdunnette/reaper --skill speckit-implement-bdunnette

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end execution of a Speck Kit implementation by processing and executing all tasks defined in tasks.md and applying the operational plan in plan.md, eliminating manual coordination and enabling repeatable, auditable workflows.

Core Features & Use Cases

  • Orchestrates phase-based execution (Setup, Tests, Core, Integration, Polish) with dependency-aware scheduling and support for parallel tasks where appropriate.
  • Validates repository readiness (presence of the .specify/ directory, tasks.md, plan.md) and enforces a test-before-implementation flow to align with the plan.
  • Handles extension and mandatory post-execution hooks via .specify/extensions.yml, provides progress reporting, and ensures tasks affecting the same files run sequentially.

Quick Start

Run speckit-implement in a repository that contains tasks.md and plan.md to automatically drive the implementation workflow from specification to completion.

Frequently Asked Questions about speckit-implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate task execution for a spec-driven workflow?

Automate spec-driven task execution by loading tasks.md and plan.md to guide the implementation workflow through sequential phases, ensuring dependency-aware scheduling and test-first development without manual coordination.

What is phase-based orchestration for software engineering tasks?

Phase-based orchestration organizes implementation into Setup, Tests, Core, Integration, and Polish stages. It enforces strict phase sequencing and dependency-aware execution to schedule parallel tasks while preventing file conflicts.

Do I need a .specify directory to run TDD-first task automation?

Yes, TDD-first task automation requires a .specify directory containing tasks.md, plan.md, and extensions.yml. The workflow validates repository readiness and enforces a test-before-implementation flow aligned with the plan.

How do I execute post-execution hooks defined in extensions.yml?

Execute post-execution hooks automatically by processing the .specify/extensions.yml configuration during the workflow. The automation enforces mandatory hooks and provides progress reporting after each task phase completes.

Can I run tasks in parallel during project automation?

Yes, project automation supports parallel task execution where appropriate based on dependency-aware scheduling. However, tasks affecting the same files are enforced to run sequentially to prevent conflicts.

What happens if my repository is missing plan.md or tasks.md?

If plan.md or tasks.md are missing, the workflow fails repository readiness validation. Both files must exist alongside the .specify directory to drive the implementation workflow from specification to completion.