plan-ceo-review

Re-evaluate product and strategy plans across four scope modes.

Updated May 7, 2026

Search Tags:#decision framework #plan review #gstack #premise challenge #founder mode #scope strategy #product ambition

Ready to run

npx skills add https://github.com/TumeloRamaphosa/StudEx-Valley-OS --skill plan-ceo-review-tumeloramaphosa

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/TumeloRamaphosa/StudEx-Valley-OS/tree/main/.claude/skills/gstack/plan-ceo-review
Command: npx skills add https://github.com/TumeloRamaphosa/StudEx-Valley-OS --skill plan-ceo-review-tumeloramaphosa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you upgrade a plan that feels too small, too narrow, or not ambitious enough by forcing a CEO-level rethink of assumptions, scope, and outcomes.

Core Features & Use Cases

Scope-mode strategy review: Runs a structured founder-style review across four explicit modes: SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, and SCOPE REDUCTION, so the plan changes deliberately instead of by vibe.
Premise challenging and dream-to-build expansion: Targets moments where a user asks to think bigger, expand scope, or re-evaluate a strategy that might be underpowered.
Grounding in prior CEO artifacts: Pulls relevant context from recent CEO plans, design docs, and prior review activity to keep the revision consistent with what was already tried and learned.

Quick Start

Use plan-ceo-review when you ask for a strategy to be more ambitious, or say something like: "Rethink my plan and expand the scope in a way that increases the chance of a 10-star product, while challenging my assumptions."

Frequently Asked Questions about plan-ceo-review

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

FAQPage Schema

How do I rethink my product strategy to build a more ambitious 10-star product?▼

To rethink product strategy for a 10-star product, you need a CEO-level review that challenges your core premises and calibrates your product ambition. This involves a structured scope strategy evaluation across expansion, selective expansion, holding, or reduction modes.

When should I use a scope expansion strategy versus a scope reduction approach?▼

You choose between scope expansion and scope reduction by running a founder-mode decision framework that reviews your current premises and desired outcomes. This structured review ensures your plan changes deliberately based on grounded context rather than by vibe.

What is the best way to challenge assumptions in a product plan that feels too narrow?▼

The best way to challenge assumptions in a narrow product plan is applying a premise challenge framework that retrieves prior CEO plans and design docs. This grounds your ambition calibration in past learnings before deciding to expand scope.

Can I review my existing design docs when calibrating product ambition?▼

Yes, you can review existing design docs during ambition calibration. The decision framework retrieves grounded context from recent CEO plans, design documents, and prior review activity to keep your scope strategy consistent with what was already tried.

How do I evaluate if my current scope strategy is underpowered?▼

You evaluate an underpowered scope strategy by running a structured plan review that forces a CEO-level rethink of your assumptions and desired outcomes. This process identifies whether selective expansion or holding scope is the optimal path forward.

Why does my strategy plan need premise challenging before expanding scope?▼

Your strategy plan needs premise challenging before expanding scope to prevent uncalibrated product ambition. A structured decision framework ensures your scope expansion targets a 10-star product outcome rather than simply increasing volume without strategic grounding.