plan-ceo-review

Reviews implementation plans with scope-mode selection, error mapping, and adversarial edge-case analysis.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/fullya99/simple-blog-page --skill plan-ceo-review-fullya99
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/fullya99/simple-blog-page/tree/main/.claude/skills/gstack/plan-ceo-review
Command: npx skills add https://github.com/fullya99/simple-blog-page --skill plan-ceo-review-fullya99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering plans often ship with silent failure modes, unhandled edge cases, missing tests, and unexamined scope assumptions. This Skill performs a rigorous, founder-grade review of any implementation plan before code is written, catching landmines early. ## Core Features & Use Cases - Three Review Modes: Choose SCOPE EXPANSION (dream big, find the 10-star product), HOLD SCOPE (maximum rigor on the agreed plan), or SCOPE REDUCTION (strip to the minimum viable version). - Ten Structured Review Sections: Covers architecture, error/rescue mapping, security threat modeling, data flow edge cases, code quality, tests, performance, observability, deployment, and long-term trajectory. - Mandatory Registries and Diagrams: Produces an error & rescue registry, failure modes registry, ASCII architecture/data-flow/state-machine diagrams, TODOS.md proposals, and a completion summary. - Use Case: Before implementing a new feature touching multiple services, run this review to map every exception class, flag unrescued errors as critical gaps, and decide interactively whether to expand, hold, or cut scope. ## Quick Start Ask the assistant to run a CEO-mode plan review on your current implementation plan and select a scope mode when prompted.

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 this plan review workflow, which starts with a system audit of git history and existing TODOs, then challenges the plan's premises and scope. It walks through ten sections covering architecture, errors, security, tests, and deployment, asking one focused question per issue found.

What is the difference between scope expansion, hold, and reduction modes?▼

Scope expansion envisions the ideal 10x product and adds delight opportunities. Hold scope accepts the plan and makes it bulletproof through rigorous edge-case and failure analysis. Scope reduction cuts everything except the minimum that ships user value.

How do I find silent failure modes in a software design?▼

The error and rescue map section lists every method that can fail, the specific exception classes, whether each is rescued, and what the user sees. Any unrescued error with silent user impact is flagged as a critical gap requiring a fix.

Does this plan review make code changes during the review?▼

No. The review explicitly forbids code changes and implementation. Its only job is to analyze the plan, ask decision questions one at a time, and produce registries, diagrams, and TODOS.md proposals for later execution.

When should I not use a full mega plan review?▼

Skip it for trivial one-line fixes or typo corrections where a ten-section review adds no value. It is designed for plans touching multiple files, new services, state machines, integrations, or anything with meaningful failure and security surface area.