CEO/Founder perspective on feature planning. Rethinks the problem to find the 10-star product hidden in the request. Four modes: Expansion, Selective Expansion, Hold Scope, Reduction. Triggers on: "ceo review", "plan ceo", "review plan", "is this the right thing to build", "rethink this"
Apply CEO/founder thinking to challenge and refine the feature plan before any code is written.
argument -- The feature idea, requirements doc, or plan to reviewIf argument is a file path, read it. Otherwise treat as inline description.
Extract and summarize:
For each assumption, ask:
Apply one of four modes:
Produce 2-3 implementation approaches with:
State clearly:
Write a refined design doc with:
CEO Review: <feature name>
Mode Applied: <Expansion|Selective|Hold|Reduction>
Original Problem: <1-2 sentences>
Refined Problem: <1-2 sentences>
Key Challenges:
- <assumption 1> → <why it's wrong/could be wrong>
- <assumption 2> → <why it's wrong/could be wrong>
Alternatives Considered:
1. <approach> - <effort> - <when to pick>
2. <approach> - <effort> - <when to pick>
Recommendation: <approach>
Design Doc: <path or inline>
<If: the user pushback indicates they've already considered your feedback> <Then: acknowledge their expertise, document their reasoning, proceed with their original approach>
<If: you identify a significantly different problem worth solving> <Then: present it as a separate recommendation, don't force it into the current plan>
<If: the scope is already minimal> <Then: focus on execution quality, not scope reduction>