Plan CEO Review

What Is This?

Overview

Plan CEO Review is a structured skill for applying founder-mode thinking to technical plans and product decisions. It provides a systematic framework for challenging assumptions, rethinking scope, and evaluating whether a proposed solution is truly the best version of what could be built. Rather than accepting the first reasonable plan, this skill pushes teams to ask harder questions before committing to implementation.

The skill operates across four distinct modes: SCOPE EXPANSION for dreaming big and reimagining the problem entirely, SELECTIVE EXPANSION for holding the core scope while cherry-picking high-value additions, HOLD SCOPE for maximum rigor and disciplined execution within defined boundaries, and SCOPE REDUCTION for stripping a plan down to its essential components. Each mode serves a different strategic moment in the development lifecycle.

This approach draws from the mindset of founders and CEOs who must constantly evaluate whether their teams are solving the right problem, not just solving the problem correctly. It is particularly valuable when a plan feels technically sound but strategically underwhelming, or when a team needs an outside perspective to validate ambition versus practicality.

Who Should Use This

• Engineering leads and technical managers reviewing project proposals before committing engineering resources
• Product managers who need a structured method for stress-testing roadmap decisions
• Founders and startup teams evaluating whether a planned feature or product direction is ambitious enough
• Senior developers who want to challenge their own plans before presenting them to stakeholders
• Architects designing systems who need to validate scope boundaries and identify missed opportunities
• Consultants and technical advisors conducting strategy reviews for client engagements

Why Use It?

Problems It Solves

• Teams often commit to technically correct plans that solve the wrong problem or miss a significantly better adjacent solution
• Scope creep and scope collapse both cause project failures, and most review processes lack a structured way to evaluate which direction is appropriate
• Plans frequently inherit flawed premises from earlier decisions, and without a deliberate challenge process those premises go unexamined
• Development workflows lack a formal checkpoint for asking whether the proposed solution is the 10-star version or merely the acceptable version
• Strategic reviews often happen informally, producing inconsistent outcomes depending on who is in the room

Core Highlights

• Four named review modes give reviewers a precise vocabulary for the type of feedback being applied
• Encourages rethinking the problem statement before evaluating the solution
• Provides a repeatable process for founder-mode thinking that does not require a founder in the room
• Surfaces hidden assumptions embedded in technical plans
• Scales from small feature decisions to large architectural choices
• Integrates naturally into existing planning and review workflows
• Produces actionable direction rather than open-ended critique

How to Use It?

Basic Usage

Invoke the skill by framing your review request with a clear mode directive. The following examples show how to structure a prompt when using this skill in a development workflow.

Review this plan using SCOPE EXPANSION mode.
Current plan: Build a CSV export feature for the reporting dashboard.

Apply HOLD SCOPE review to the following API design.
Constraint: Must ship in two weeks with current team capacity.

Run a SCOPE REDUCTION review on this architecture proposal.
Goal: Identify the minimum viable version that delivers core value.

Specific Scenarios

When a team presents a plan that feels safe but uninspiring, use SCOPE EXPANSION to force the question of what the ideal version of this product would look like if constraints were temporarily removed. When a plan has grown unwieldy through committee input, use SCOPE REDUCTION to identify what can be cut without losing the core value proposition.

Real-World Examples

A team planning a basic notification system receives a SELECTIVE EXPANSION review that keeps the core email notification scope but adds a single high-value addition: a unified preference center that prevents future rework. A startup reviewing its MVP roadmap uses SCOPE REDUCTION to cut three planned features and ship two weeks earlier with a cleaner product.

Important Notes

Requirements

• A written plan or proposal must exist before applying the review, as the skill requires a concrete artifact to evaluate
• The reviewer must select a mode before beginning, since mixing modes within a single review produces inconsistent feedback
• Stakeholders should agree on the review mode in advance to avoid misaligned expectations about the output