plan-ceo-review

Review product plans with four scope modes and structured debate prompts.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/fray-cloud/coin --skill plan-ceo-review-fray-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/fray-cloud/coin/tree/main/.claude/skills/gstack/plan-ceo-review
Command: npx skills add https://github.com/fray-cloud/coin --skill plan-ceo-review-fray-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CEO/founder-mode plan reviews help teams rethink problems, identify the 10x product opportunities, and challenge premises to push scope where it adds real value. It guides users through four modes—SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, and SCOPE REDUCTION—to ensure plans are ambitious yet practical. The skill acts as a rigorous, founder-leaning auditor that surfaces bets, assumptions, and gaps before committing to execution.

Core Features & Use Cases

  • Four modes: SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, SCOPE REDUCTION.
  • Proactively surfaces improvements, risks, and tradeoffs to create a stronger, more actionable roadmap.
  • Produces structured prompts and decision logs to facilitate cross-functional alignment in strategy reviews.

Quick Start

Ask it to run a CEO-style plan review on the current plan and propose scope changes.

Frequently Asked Questions about plan-ceo-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a CEO-style plan review to challenge product strategy assumptions?

A CEO-style plan review challenges product strategy assumptions by applying founder-mode reasoning to surface bets, risks, and gaps. It uses structured prompts and four scope modes to guide debates and align cross-functional teams on an ambitious, actionable roadmap.

When do I need a scope expansion review for my product roadmap?

You need a scope expansion review when your product roadmap lacks high-ambition opportunities and requires problem reframing. This review mode pushes scope where it adds real value, identifying 10x product opportunities by challenging existing premises before execution.

How do I decide between scope expansion and selective expansion during a strategy review?

Decide between scope expansion and selective expansion by evaluating clear criteria for scope decisions during strategy sessions. Scope expansion broadly pushes boundaries for 10x opportunities, while selective expansion targets specific high-value areas to keep the plan practical.

Can I use a plan review skill for early-stage startup roadmap design?

Yes, you can use this plan review approach for early-stage or growth-stage startup roadmap design. It acts as a rigorous founder-leaning auditor to rethink problems, identify product opportunities, and ensure your roadmap is ambitious yet practical before committing to execution.

What is the best way to reduce scope and align on a practical product plan?

The best way to reduce scope and align on a practical product plan is applying the scope reduction mode within a structured plan review. It proactively surfaces tradeoffs and risks, producing decision logs that facilitate cross-functional alignment while stripping non-essential features.

Why does my roadmap strategy fail to surface high-ambition product bets?

Your roadmap strategy may fail to surface high-ambition product bets because it lacks rigorous founder-mode challenge sessions. Without applying structured scope debates and assumption audits, plans often miss 10x opportunities and fail to push scope where it adds real value.