plan-ceo-review

Review product plans by selecting scope levels and challenging key premises.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/yashs33244/my-mac-claude --skill plan-ceo-review-yashs33244
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/yashs33244/my-mac-claude/tree/main/skills/gstack/plan-ceo-review
Command: npx skills add https://github.com/yashs33244/my-mac-claude --skill plan-ceo-review-yashs33244

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review a product or engineering plan when it feels too small, unclear, or insufficiently ambitious, so you can choose the right level of scope and execution rigor.

Core Features & Use Cases

  • Four-mode CEO/founder review: Use SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, or SCOPE REDUCTION to match how ambitious the plan should be.
  • Premise challenge and scope calibration: Explicitly challenge underlying assumptions and adjust the plan’s breadth to improve product value.
  • Project-aware context loading: Pulls prior CEO plans, recent design docs, and recent review activity to ground the decision in what you already tried.
  • Best used for strategic prompts: Ideal when asked to think bigger, expand scope, rethink a strategy, or assess whether ambition is “enough.”

Quick Start

Ask your AI to run plan-ceo-review and tell you which of the four scope modes to use for your plan, what assumptions to challenge, and what concrete scope changes to make.

Frequently Asked Questions about plan-ceo-review

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

FAQPage Schema
How do I review my product roadmap to ensure it is ambitious enough?

Strategy refreshes use scope calibration to challenge underlying assumptions and adjust plan breadth. By reframing your product strategy through selective expansion or scope reduction, you align roadmap planning with desired ambition and execution rigor.

What is the best way to expand product scope without losing design alignment?

The best way to expand product scope while maintaining design alignment is through selective expansion. This mode reviews prior design docs and CEO plans to ground scope changes in existing context, ensuring you only expand areas that improve product value.

When do I need to use scope reduction during roadmap planning?

You need scope reduction during roadmap planning when your product or engineering plan feels too broad or lacks execution rigor. This approach challenges your underlying premises and narrows the plan's breadth to ensure high-quality delivery.

Can I challenge underlying assumptions in my engineering plan before execution?

Yes, you can challenge underlying assumptions in your engineering plan through premise testing during a scope review. This identifies weak premises and adjusts the plan's scope level, ensuring your execution rigor matches the required roadmap ambition.

Does this CEO mode scope review work without prior design docs?

While the scope review can function independently, it is designed to pull prior CEO plans and recent design docs to ground decisions. Loading this project-aware context provides a baseline for premise testing and scope calibration.