plan-ceo-review

Review product plans using four CEO-mode scope strategies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Founder and product teams often chase ambitious ideas without explicit strategy or scope guards. This Skill provides a disciplined framework to rethink plans, surface high-impact directions, and align on what to expand, hold, or reduce.

Core Features & Use Cases

  • Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials).
  • Structured prompts and checks to surface premises, required resources, and risk.
  • Use Case: when evaluating a new product plan, run a CEO-review to surface missing assumptions and align on a 10-star product.

Quick Start

Proactively run a CEO-review on your current plan to identify gaps and expansion opportunities.

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-level product strategy review on my current plan?

A CEO-level product strategy review evaluates your plan using four scope modes—expansion, selective expansion, hold, and reduction—to surface premises, identify risks, and align on high-impact directions.

What is the best framework for challenging product strategy premises and expanding scope?

A structured decision framework for scope management challenges premises by applying structured checks to surface required resources and risks, guiding teams to rethink problems and elevate product directions.

When should I use scope reduction instead of scope expansion for product planning?

Use scope reduction to strip plans to essentials when maximum rigor is needed, whereas scope expansion applies when asked to dream big and rethink problems for high-potential directions.

Can I use product strategy review tools to surface missing assumptions in a new plan?

Yes, a plan review framework surfaces missing assumptions by reasoning over premises and gathering context to identify gaps, ensuring alignment on a high-potential product direction.

Does the CEO mode plan review require any specific toolset to gather context?

The CEO mode plan review leverages the gstack toolset, utilizing Read, Grep, Glob, Bash, AskUserQuestion, and WebSearch to gather context, reason over premises, and surface recommendations.