plan-ceo-review

Reviews implementation plans with CEO-mode scope analysis and rigor checks.

2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/westkite1201/garden-engine --skill plan-ceo-review-westkite1201
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/westkite1201/garden-engine/tree/main/.claude/skills/gstack/plan-ceo-review
Command: npx skills add https://github.com/westkite1201/garden-engine --skill plan-ceo-review-westkite1201

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans often ship with unchallenged premises, hidden failure modes, and scope that is either too timid or too bloated. This Skill performs a founder-mode review of an implementation plan before any code is written, catching landmines early and forcing explicit scope decisions. ## Core Features & Use Cases - Four Review Modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope plus cherry-picked expansions), HOLD SCOPE (maximum rigor), and SCOPE REDUCTION (strip to essentials), each chosen explicitly by the user. - System Audit and Failure Mapping: Runs a pre-review audit of git history, TODOs, and design docs, then maps error paths, shadow data flows, edge cases, and observability gaps. - Structured Decision Gates: Every scope change is presented as an individual AskUserQuestion with recommendations and completeness scores, so the user stays in control. - Use Case: Before implementing a new feature, run this review to challenge whether the plan is ambitious enough, verify every error path is named and tested, and produce a GSTACK REVIEW REPORT appended to the plan file. ## Quick Start Ask the AI to run a CEO review on the current branch's plan and challenge whether the scope is ambitious enough.

Frequently Asked Questions about plan-ceo-review

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

FAQPage Schema
How do I review an implementation plan before writing code?

Run a structured plan review that audits recent git history, maps error paths and failure modes, and challenges scope decisions. This Skill walks through each decision as an explicit question with recommendations and completeness scores.

What are the four review modes in plan-ceo-review?

The modes are SCOPE EXPANSION (push ambition upward), SELECTIVE EXPANSION (hold scope but cherry-pick expansions), HOLD SCOPE (maximum rigor on the existing plan), and SCOPE REDUCTION (cut to the minimum viable version). The user picks one and every scope change stays an explicit opt-in.

Does the CEO plan review require a design doc?

No, but it checks for one. If no design doc exists for the branch, it offers to run the office-hours skill first to produce a structured problem statement, then continues the review with that sharper input.

Can the review modify my code or start implementation?

No. The skill explicitly forbids code changes and implementation. Its only job is reviewing the plan, and in plan mode it may only append a GSTACK REVIEW REPORT section to the plan file.

What happens when the plan review finds issues outside my branch?

It follows the repo ownership mode. In solo repos it investigates and offers to fix proactively; in collaborative repos it flags the issue via a question instead of fixing it, since it may be someone else's responsibility.