plan-execute

Executes an approved plan step-by-step with drift detection and explicit verification gates.

14|1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/allemaar/open-skills --skill plan-execute-allemaar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-execute
Source: https://github.com/allemaar/open-skills/tree/main/skills/plan-execute
Command: npx skills add https://github.com/allemaar/open-skills --skill plan-execute-allemaar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Approved plans often get executed with silent deviations, unspoken judgment calls, and unverified outcomes. This Skill enforces disciplined execution: follow the plan exactly, stop on drift, surface every judgment call, and end with an explicit completion declaration. ## Core Features & Use Cases - Plan Validation Gate: Rejects plans lacking numbered steps, concrete actions, or verifiable outcomes before any work begins. - Drift and Judgment-Call Handling: Stops immediately when reality differs from the plan or when an unspecified decision is required, asking the user instead of improvising. - Verification and Terminal Declaration: Runs the plan's verification steps plus the project's gate suite (lint/test/typecheck), maps each step to its verification, and always ends with a complete, failed, or halted declaration. - Use Case: After approving an implementation plan with /plan-create, run /execute to have the agent implement each step in order, pause for your approval on any deviation, and report exactly what was verified before committing. ## Quick Start After approving a plan in your conversation, say "execute the plan" to have the agent implement it step by step with verification.

Frequently Asked Questions about plan-execute

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

FAQPage Schema
How do I execute an approved plan with an AI coding agent?

Run /execute or say "execute the plan" after a plan has been approved. The agent loads the plan from conversation context, PLAN.md, or implementation_plan.md, then performs each numbered step in order and reports verification results.

What makes a plan valid for automated execution?

A valid executable plan needs numbered steps, concrete actions naming what to do rather than what to achieve, and at least one verifiable outcome. Plans missing these are rejected at the alignment gate with the specific gap named.

What happens when the codebase differs from what the plan assumed?

Execution stops immediately when drift is detected. The agent states the planned versus found discrepancy and asks you to approve a specific deviation or revise the plan, rather than self-correcting silently.

Does plan execution run tests before committing code?

Yes, when execution produces committable code it runs the project's defined gate suite such as lint, test, and typecheck as a deliberate pre-commit gate. Each plan step's outcome is mapped to its verification, and skipped gates are named explicitly.

When should I not use plan-execute?

Do not use it when no plan exists yet or when you only want to inspect a plan. Use /plan-create to design a plan first, or /plan-deep-dive to examine one without running it.