plan-ceo-review

Analyze product plans to surface gaps, risks, and opportunities for CEO-level refinement.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CEO/founder-mode plan review framework that challenges assumptions, surface gaps, and aligns plans with high-level strategic goals to produce robust, CEO-ready roadmaps.

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 workflow: system audit, risk/rescue mapping, and diagrammatic outputs to reveal failure modes and dependencies.
  • Collaboration guardrails: supports asks for design-docs / office-hours inputs and formats decisions for executive reviews.

Quick Start

Describe your plan in CEO-review mode and select a mode to proceed.

Frequently Asked Questions about plan-ceo-review

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

FAQPage Schema
How do I prepare a product plan for a CEO-level review?

Preparing a product plan for a CEO-level review involves analyzing strategy and scope decisions to surface gaps, risks, and opportunities. The framework challenges assumptions and aligns multi-quarter plans with high-level strategic goals for executive refinement.

What is scope reduction in strategic roadmap planning?

Scope reduction in strategic roadmap planning is a decision mode that strips multi-quarter plans to their essential components. It applies guardrails to constrain scope, ensuring focused execution when tightening product strategy.

How do I analyze risks and dependencies for a multi-quarter roadmap pivot?

Analyzing risks and dependencies for a multi-quarter roadmap pivot requires mapping failure modes through system audits and risk rescue mapping. This produces diagrammatic outputs and risk flags revealing critical dependencies for scope decisions.

When should I use selective expansion versus hold scope for product strategy?

Use selective expansion to cherry-pick strategic additions while holding existing scope, whereas hold scope enforces maximum rigor on current boundaries. Selective expansion suits targeted growth opportunities, while hold scope tightens strategy without expanding.

Can I use this framework for major scope decisions without design docs?

You can use the framework for major scope decisions without design docs, but collaboration guardrails support asks for design docs and office-hours inputs. Providing these inputs improves the quality of risk flags and decision criteria for executive reviews.

What are the limitations of using a four-mode framework for executive plan reviews?

The four-mode framework limits decisions to scope expansion, selective expansion, hold scope, or scope reduction. It may not capture nuances outside these categories, requiring additional strategic analysis for highly unconventional product scenarios.