executing-plans

Execute implementation plans with review checkpoints and verification gates.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/yckkkk/reo --skill executing-plans-yckkkk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/yckkkk/reo/tree/main/.agents/skills/executing-plans
Command: npx skills add https://github.com/yckkkk/reo --skill executing-plans-yckkkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables execution of a written implementation plan in a separate session with review checkpoints, ensuring disciplined progress and verifiable outcomes.

Core Features & Use Cases

  • Plan loading and critical review: Inspect plan before execution to identify gaps or questions.
  • Stepwise execution and verification: Execute tasks one by one with status tracking and verification gates.
  • Blocker handling and escalation: Pause on blockers and prompt for human input when necessary.
  • Integration-ready workflow: Works with sub-skills for isolated workspaces, plan creation, and branch finishing.

Quick Start

Load the plan file, review it for gaps, and begin executing tasks exactly as written.

Frequently Asked Questions about executing-plans

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

FAQPage Schema
How do I execute a development plan with verification gates?

To execute a development plan, load the plan file and review it for gaps before starting. The system tracks stepwise execution and applies verification gates after each task to ensure disciplined progress and verifiable outcomes.

What is plan-driven development and when do I need it?

Plan-driven development is an isolated-workspace workflow that executes written implementation plans with explicit checkpoints. You need it to ensure safe, auditable progress across tasks, verifications, and blocker handling during software engineering.

How do I handle blockers when executing an implementation plan?

When encountering blockers during implementation plan execution, the workflow pauses and prompts for human input. This escalation mechanism ensures issues are resolved before proceeding to the next verification checkpoint.

Can I use git worktrees to isolate development branches during plan execution?

Yes, the workflow enforces an isolated-workspace environment using git worktrees. This integration ensures safe, auditable execution by separating the development branch while running tasks and verifications.

Does plan execution work without a pre-written plan file?

No, this workflow requires a written plan file as input. It inspects the plan before execution to identify gaps or questions, relying on plan creation subskills to provide the structured tasks and verifications needed for disciplined progress.

What is the best way to review an implementation plan before executing it?

The best way to review an implementation plan is to load the file and inspect it for gaps or questions before execution begins. This critical review step ensures the tasks, verifications, and checkpoints are complete and actionable.