plan-ceo-review

Critique product strategy plans across four scope modes.

37|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/DariusCorvus/iqualize --skill plan-ceo-review-dariuscorvus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/DariusCorvus/iqualize/tree/main/.claude/skills/gstack/plan-ceo-review
Command: npx skills add https://github.com/DariusCorvus/iqualize --skill plan-ceo-review-dariuscorvus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides founders and product leaders through rigorous, high-ambition plan reviews. It helps reframe problems, surface bold 10-star product ideas, and challenge premises to raise the bar.

Core Features & Use Cases

  • Four modes for planning: SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, SCOPE REDUCTION, enabling flexible strategy exploration.
  • Structured frontmatter-driven plan metadata and a repeatable review workflow that surfaces risks, dependencies, and tradeoffs.
  • Use during strategy sessions, roadmap planning, and exec reviews to align teams on a clear, ambitious path.

Quick Start

Ask me to run a CEO-review with plan-ceo-review and select a mode.

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 product strategy review to challenge roadmap premises and expand scope?

A product strategy review critiques existing plans to maximize impact by reframing scope and surfacing bold expansions. You run a structured, mode-driven workflow that evaluates roadmap narratives and identifies tradeoffs during strategy sessions.

What is scope expansion in product management and when should I use it?

Scope expansion in product management is a planning mode that reframes problems to surface high-ambition, 10-star product ideas. Use it during strategy sessions or roadmap planning when you need to challenge premises and boldly raise the bar on product impact.

How do I choose between scope expansion, selective expansion, hold scope, and scope reduction?

Choosing between scope expansion, selective expansion, hold scope, and scope reduction depends on your strategic goals and risk analysis. Each mode guides a different level of roadmap critique, allowing flexible strategy exploration from aggressive growth to focused refinement.

Can I use a CEO review workflow for team critiques and exec reviews?

Yes, you can use a CEO review workflow for team critiques and exec reviews. It provides a repeatable process to align teams on a clear, ambitious path by surfacing risks, dependencies, and tradeoffs within a structured plan narrative.

What do I need to prepare before running a mode-driven plan critique?

Before running a mode-driven plan critique, you need clear frontmatter metadata defining the plan, a robust plan narrative, and a defined mode-driven workflow. These inputs ensure the strategy review operates safely and surfaces meaningful risks and tradeoffs.

When should I not use scope reduction during roadmap planning?

You should not use scope reduction during roadmap planning when your goal is to surface bold 10-star product ideas and aggressively raise ambition. Scope reduction is for focused refinement, whereas high-impact strategy sessions require the scope expansion mode.