impl-spec-executor

Execute implementation specs via topic branches, per-phase subagents, and review gates.

Updated Jan 8, 2026

Search Tags:#automation #code-review #git-workflow #security-review #phase-review #spec-execution

Ready to run

npx skills add https://github.com/elertan/planspec --skill impl-spec-executor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: impl-spec-executor
Source: https://github.com/elertan/planspec/tree/main/skills/impl-spec-executor
Command: npx skills add https://github.com/elertan/planspec --skill impl-spec-executor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end execution of implementation specs by coordinating topic branches, per-phase subagents, and gated reviews, surfacing blockers only when auto-resolution fails.

Core Features & Use Cases

Orchestrates a phased execution pipeline: Initialize, Phase Implementations, Phase Checkpoints, and Completion.
Spawns and manages per-phase subagents for implementation tasks and both code and security reviews.
Enforces review gates and blockers via a task system, surfacing unresolved issues to users for guidance.

Quick Start

Instruct planspec:impl-spec-executor with your impl-spec file to start the automated workflow.

Frequently Asked Questions about impl-spec-executor

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

FAQPage Schema

How do I automate implementation spec execution with phased reviews?▼

Automating implementation spec execution involves creating a topic branch, spawning per-phase subagents for implementation, and enforcing gated code and security reviews. This workflow requires a ready impl-spec file, a linked design spec, and a clean working directory to orchestrate end-to-end development.

What is a topic branch workflow for automated spec execution?▼

A topic branch workflow for spec execution isolates feature development by creating a dedicated branch, then systematically processing implementation phases through subagents. It coordinates phased checkpoints and review gates to ensure code quality before merging automated software engineering tasks.

How do I set up prerequisites for automated spec execution?▼

Setting up automated spec execution requires an impl-spec file with status ready, a linked design spec, and a clean working directory. You also need a task system configured to track per-phase subagents and manage blockers surfaced during gated code and security reviews.

How does automated code review handle blockers during spec execution?▼

Automated code review handles blockers by enforcing review gates at each phase checkpoint using subagents. When auto-resolution fails during the implementation spec execution, the system surfaces unresolved issues to users for guidance rather than proceeding with the workflow.

Can I run security reviews automatically within a phased development pipeline?▼

Yes, you can run security reviews automatically within a phased development pipeline by spawning reviewer subagents at each phase checkpoint. The automated workflow enforces these security review gates alongside code reviews, halting execution and surfacing blockers if auto-resolution fails.

When should I avoid using automated subagents for spec execution?▼

You should avoid using automated subagents for spec execution when your working directory is not clean, when your impl-spec file lacks a ready status, or when no linked design spec exists. The workflow requires these exact prerequisites to function properly.