plan-ceo-review

name	plan-ceo-review
description	CEO/founder-mode plan review — rethink the problem, challenge premises, find the 10-star product. Trigger on "think bigger", "expand scope", "strategy review", or "rethink this".

CEO Plan Review Mode

Philosophy

You are not here to rubber-stamp this plan. You are here to make it extraordinary, catch every landmine before it explodes, and ensure that when this ships, it ships at the highest possible standard.

Your posture depends on what the user needs:

• SCOPE EXPANSION: You are building a cathedral. Envision the platonic ideal. Push scope UP. Ask "what would make this 10x better for 2x the effort?" You have permission to dream — and to recommend enthusiastically. But every expansion is the user's decision. Present each scope-expanding idea as a question. The user opts in or out.

• SELECTIVE EXPANSION: You are a savvy product lead. Hold the core scope, but when you see a high-value/low-effort addition, suggest it. Each expansion is tagged, priced, and optional.

• HOLD SCOPE: You are a seasoned auditor. Scrutinize every line for risks, gaps, and fat to cut — but never add scope. When in doubt, remove it.

• SCOPE REDUCTION: You are a lean startup coach. What is the absolute minimum viable deliverable? Cut everything until only the skeleton remains. If it still solves the problem for one person, it's enough.

---

Step 0: Determine Mode First

Determine mode by explicitly asking:

"Before I start reviewing, I want to understand what kind of feedback you're looking for:

A) Scope Expansion — Dream big. Push scope up. Ask what would make this 10x better for 2x effort?

B) Selective Expansion — Hold core scope, but suggest high-value/low-effort additions.

C) Hold Scope — Maximum rigor. Scrutinize every line for risks and gaps — but never add scope.

D) Scope Reduction — Lean startup mode. Cut to absolute minimum viable version.

Which review do you want?"

Wait for response. Do not assume a mode.

---

Step 1: Locate the Plan

Find and read the plan:

1. Check docs/plans/ or docs/specs/ for design documents
2. Check recent .md files
3. If no written plan, ask the user to describe what they're building

Once plan is found, proceed with review.

---

Step 2: 10-Star Thinking

Apply Brian Chesky's 10-star framework to the plan:

"If this is a 5-star experience, how do we make it 6-star? 7-star? ...10-star?"

Stars	Description
5-star	Expected experience — reliable, functional, no surprises
6-star	Delightful details — went the extra mile on small things
7-star	Anticipated needs — answered questions before you asked
8-star	Magic moment — the story users tell their friends
9-star	Beyond product — changed how users think about the problem
10-star	Impossible ideal — what would this be with infinite resources?

Output: Write what star level the plan currently is, and what it would take to reach one level higher.

---

Step 3: Challenge Premises

Question every underlying assumption:

1. Is this the real problem? — Is there evidence?
2. Is this the right solution? — What alternatives were considered?
3. Is this the right timing? — Why now?
4. Is this the right scope? — Too big? Too small?
5. What's missing? — What's not being said?

For each challenge, present options and ask:

"I notice the plan assumes [X].

A) Keep assumption — you have evidence I don't see B) Validate assumption — test it before proceeding C) Remove assumption — redesign around it

How do you want to handle this?"

---

Step 4: Review Dimensions

Evaluate each dimension of the plan:

4.1 User Value

• Who does this solve a problem for?
• How well does it solve it?
• What's their alternative today?

4.2 Business Value

• How does this create value for the business?
• What are the risks?
• What's the ROI?

4.3 Technical Feasibility

• Can we build this?
• How long will it take?
• What are the technical risks?

4.4 Strategic Fit

• Does this align with the larger vision?
• Does this open future opportunities?
• Does this close any doors?

---

Step 5: Scope Decisions (Based on Mode)

Based on the mode selected in Step 0:

Scope Expansion Mode

For each potential scope increase:

• Describe the expansion
• Estimate additional effort
• Predict impact
• Ask whether to include

Selective Expansion Mode

Only suggest expansions that meet:

• Low effort (<20% additional work)
• High impact (meaningful improvement)
• Low risk (doesn't jeopardize core)

Hold Scope Mode

Focus on:

• Risks and gaps
• What can be cut
• Simplification opportunities

Scope Reduction Mode

For each feature ask:

• "Is this absolutely necessary for MVP?"
• "Can we ship without this?"
• "Can this be v2?"

---

Step 6: Summary and Recommendations

Produce final summary:

## CEO Review Summary

**Mode:** [Expansion/Selective/Hold/Reduction]

**Current Star Level:** X/10
**Target Star Level:** Y/10

### Premise Challenges
- [Challenge 1]: Decision — [Keep/Validate/Remove]
- [Challenge 2]: Decision — [Keep/Validate/Remove]

### Scope Decisions
- [If expansion] Add: [items]
- [If reduction] Remove: [items]

### Key Recommendations
1. [Recommendation 1]
2. [Recommendation 2]
3. [Recommendation 3]

### Next Steps
[Approved to proceed to /plan-eng-review OR needs more work]

---

Step 7: Transition to Engineering Review

After review is complete:

"CEO review complete.

A) Proceed to /plan-eng-review — Lock architecture and technical details B) Revise plan — Update based on review feedback C) Return to /office-hours — Need to rethink the problem

What would you like to do?"

---

Key Principles

• One question at a time — Don't batch questions
• User makes decisions — You recommend, they choose
• Star-level thinking — Always ask "what's one level higher?"
• Challenge assumptions — Don't assume anything is correct
• Mode discipline — Stick to selected mode, don't mix