speckit-implement

Execute Speckit implementation tasks from tasks.md and plan.md with progress tracking.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/burningddol/epigram --skill speckit-implement-burningddol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-implement
Source: https://github.com/burningddol/epigram/tree/main/.claude/skills/speckit-implement
Command: npx skills add https://github.com/burningddol/epigram --skill speckit-implement-burningddol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates and executes the full Speckit implementation plan by parsing tasks.md, plan.md, and related validation rules to drive end-to-end project execution.

Core Features & Use Cases

  • Orchestrates phase-based work (Setup, Tests, Core, Integration, Polish) according to tasks.md.
  • Enforces TDD workflow by running tests before corresponding implementations and tracking progress across phases.
  • Validates dependencies, checks for extension hooks and ignore file policies, and reports blockers before proceeding.

Quick Start

Run the speckit-implement skill to execute all tasks defined in tasks.md and generate a progress report.

Frequently Asked Questions about speckit-implement

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

FAQPage Schema
How do I automate end-to-end implementation of a Speckit plan?

To enforce a TDD workflow during project execution, the system runs tests before corresponding implementations and tracks progress across phases. It validates dependencies, checks extension hooks, and reports blockers before proceeding to subsequent tasks.

What is the best way to manage task dependencies and extension hooks in a structured project plan?

Managing task dependencies and extension hooks requires parsing validation rules within your project planning files. The execution process verifies prerequisites, applies ignore file policies, and reports blockers before proceeding to dependent tasks.

Do I need specific planning files to start automated phase-based project execution?

Yes, automated phase-based project execution requires tasks.md and plan.md files to define the work. These files provide the structured task definitions, dependency mappings, and validation rules necessary to drive the end-to-end implementation.

Why does my automated implementation workflow pause before moving to the next phase?

An automated implementation workflow pauses when it encounters blockers, fails prerequisite verification, or detects missing dependencies. The system validates these conditions and reports issues before proceeding to ensure structured task execution integrity.

Can I integrate ignore file handling and prereq verification into my project automation?

Yes, you can integrate ignore file handling and prereq verification into your project automation. The execution workflow automatically checks for ignore file policies and verifies prerequisites before driving subsequent project activity and generating progress reports.