executing-plans

Coordinate plan execution in batches with critical review checkpoints.

22|4|Updated Oct 28, 2025
One-click install
npx skills add https://github.com/ivfarias/ceo --skill executing-plans-ivfarias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/ivfarias/ceo/tree/main/.gemini/skills/executing-plans
Command: npx skills add https://github.com/ivfarias/ceo --skill executing-plans-ivfarias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill coordinates the execution of a written plan by introducing critical review checkpoints and batch-driven progress, reducing risk of misalignment and rework.

Core Features & Use Cases

  • Batch-based execution: run plan steps in controllable batches with verification between batches.
  • Critical review: identify concerns before starting execution and escalate blockers.
  • Progress reporting: document completed work and outcomes for partner review.

Quick Start

Start by loading the plan, reviewing it for gaps, and then execute the first batch of up to three tasks with built-in verifications.

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 in batches with verification checkpoints?

Plan execution in batches involves running up to three tasks sequentially, applying strict verifications, and pausing for critical review feedback before proceeding to the next batch. This structured approach reduces rework risk by catching misalignment early between batch intervals.

What is the best way to handle blockers during structured plan execution?

Handling blockers during plan execution requires identifying concerns during critical review checkpoints and escalating them immediately. The workflow pauses batch progress to await partner feedback, ensuring blockers are resolved and documented before subsequent tasks begin.

How do I record progress and outcomes for partner review during batch execution?

Progress reporting during batch execution is handled by documenting completed work and outcomes within each batch interval. The workflow pauses after verification, generating a progress record that awaits partner review before initiating the next set of tasks.

Can I use sub-skills to complete a development branch after finishing plan batches?

Yes, when needed, the workflow integrates the ceo:finishing-a-development-branch sub-skill to complete development after batches are executed. This handles the final branch completion following strict verifications and batch progress reporting.

Does batch-based plan execution require a pre-written plan to start?

Yes, batch-based plan execution starts by loading an existing written plan and reviewing it for gaps. You must input a defined plan to coordinate the batch-driven workflow, apply critical review checkpoints, and manage task execution effectively.