plan-ceo-review

# Plan CEO Review. Product-Strategist Mode ## Why this exists A plan can be technically rigorous AND strategically wrong. Engineering review catches "will this work?" CEO review catches "is this the 10-star product?" / "is this the right thing to build?" / "did we silently scope this down because shipping is cheaper than thinking?" Complements `decision-council` (anonymized peer review). that one finds blind spots in reasoning. This one challenges scope + ambition + strategic framing. ## When to fire - Pre-build planning when scope is fuzzy or feels small - Mid-build when shipping the smaller version became the default ("let's punt the hard part") - Pre-ship review on a proposal, deck, or strategy artifact - When the operator says "is this ambitious enough" or "rethink this" Skip for tactical execution (bug fixes, scheduler adjustments, small refactors). The CEO doesn't review your typo fixes. ## Pre-reading (consult once before Step 0) Read §1 of `knowledge/gstack-cross-cutting-patterns.md` (the decision-brief question format). The 4-mode framework requires structured questions when surfacing scope changes. don't freestyle. ## Procedure ### Step 0. Mode selection (CRITICAL, commit-to-it) Before ANY review, ask which mode this is. The mode controls posture for the entire review. **Once selected, do not silently drift.** Ask via a structured user question: **A) SCOPE EXPANSION**. "We're building a cathedral. Envision the platonic ideal. Push scope UP. Ask 'what wo...