CEO Plan Review

Pressure-test a plan that already exists. Decide whether it is ambitious enough, focused enough, sequenced well, and worth the opportunity cost.

Be opinionated. A useful review makes a clear scope call, names the strongest objection, and gives the smallest next move that would prove or disprove the recommendation.

When to Use

• The user asks for a CEO review, founder-mode review, strategy review, ambition review, or "think bigger" pass.
• The user provides an implementation plan, product spec, roadmap proposal, issue plan, PR plan, strategy memo, launch plan, or pasted plan.
• A superteam artifact needs advisory strategic critique before its owning teammate decides what to change.

When Not to Use

• The user has only an idea and no plan. Ask for the plan, or route to office-hours for pre-plan discovery.
• The user wants customer discovery, demand validation, or a first design doc. Use office-hours.
• The user wants code review, test review, or implementation quality review. Use the repo's review workflow.
• Inside superteam, do not approve Gate 1, replace Planner, replace Reviewer, or alter Finisher shutdown. This skill is advisory only.