plan-ceo-review

Plan CEO-level strategy reviews using four scope modes and decision criteria.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Scivor/helm --skill plan-ceo-review-scivor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/Scivor/helm/tree/main/skills/gstack/plan-ceo-review
Command: npx skills add https://github.com/Scivor/helm --skill plan-ceo-review-scivor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan gaps in early product strategy by forcing a CEO-level critique of problems, opportunities, and scope. It helps teams quickly challenge assumptions, rethink the problem space, and identify a 10-star product concept.

Core Features & Use Cases

  • Four modes to shape scope: SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, SCOPE REDUCTION. Each mode provides guidance on when to broaden or tighten the plan and how to audit tradeoffs.
  • Proactive prompting and guided questioning to surface high-impact pivots and align stakeholders around a coherent roadmap.
  • Structured outputs to capture decisions, premises, and next steps during strategy reviews.

Quick Start

Summarize the current plan in a CEO tone, name one ambitious expansion and one riskiest assumption, and outline the next-step test for the sprint.

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 a product roadmap from a CEO perspective?

To review a product roadmap from a CEO perspective, you summarize the current plan, identify an ambitious scope expansion, name the riskiest assumption, and outline a next-step test for the sprint to challenge premises and adjust scope.

What is the best way to challenge assumptions during a startup strategy refresh?

The best way to challenge assumptions during a startup strategy refresh is using a four-mode framework that forces explicit decision criteria and proactive questioning to surface high-impact pivots and align stakeholders around a coherent roadmap.

How do I decide whether to expand or reduce scope during a product pivot?

To decide whether to expand or reduce scope during a product pivot, apply the four scope modes—Scope Expansion, Selective Expansion, Hold Scope, and Scope Reduction—which guide when to broaden or tighten the plan and how to audit tradeoffs.

Can I use a structured framework to identify a 10-star product concept?

Yes, you can use a structured framework to identify a 10-star product concept by forcing a CEO-level critique of problems and opportunities, capturing decisions and premises, and running completeness checks to iterate on the plan.

What should I do when scope debates stall early product strategy planning?

When scope debates stall early product strategy planning, use guided questioning to rethink the problem space, apply explicit decision criteria, and structure outputs to capture next steps and align stakeholders.

Are there limitations to using a four-mode framework for roadmap pivots?

A limitation of using a four-mode framework for roadmap pivots is that it requires explicit decision criteria and a plan to iterate with completeness checks, meaning it demands structured inputs and proactive stakeholder alignment to function effectively.