plan-ceo-review

Review product or project plans for scope, premises, and execution quality.

6|2|Updated Oct 18, 2021
One-click install
npx skills add https://github.com/jerrywu001/jerrywu001 --skill plan-ceo-review-jerrywu001
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/jerrywu001/jerrywu001/tree/main/.claude/skills/plan-ceo-review
Command: npx skills add https://github.com/jerrywu001/jerrywu001 --skill plan-ceo-review-jerrywu001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you challenge whether a plan is ambitious enough—or too ambitious—by rethinking the problem, questioning assumptions, and steering scope toward a 10-star outcome.

Core Features & Use Cases

  • Mode-based scope review: Choose how aggressive to be (dream big, hold rigor, selectively expand, or cut to essentials) and apply that consistently.
  • Premise challenge & inversion: Identify what could make the plan fail, surface hidden landmines, and name specific failure modes and missing edge cases.
  • Rigor-first deliverables: Produce a structured review that emphasizes observability, error paths, diagrams, and what must be written down before implementation.

Use cases: Use it when you’re being asked to “think bigger,” “expand scope,” do a strategy review, or feel uncertain whether a plan is ambitious enough.

Quick Start

Ask the AI: Review my plan like a CEO in SCOPE EXPANSION mode and tell me the highest-impact changes to make it a 10-star product with named failure modes, edge cases, and observability requirements.

Frequently Asked Questions about plan-ceo-review

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

FAQPage Schema
How do I stress-test a product plan to check if it is ambitious enough?

Stress-test a product plan by applying a mode-based scope review that questions premises, identifies failure modes, and steers scope toward a 10-star outcome. You select an aggressive or conservative mode and evaluate ambition accordingly.

What is the best way to identify hidden risks and failure modes in a project strategy?

Identify hidden risks through premise challenge and inversion techniques that surface what could make the plan fail, name specific failure modes, and map out missing edge cases before implementation begins.

Can I selectively expand scope during a strategy review without losing execution rigor?

Yes, you can selectively expand scope by choosing the appropriate scope expansion mode, which requires explicit user opt-in for changes and enforces execution rigor through comprehensive error-path mapping and observability requirements.

How do I conduct a CEO-level review of my product planning assumptions?

Conduct a CEO-level review by challenging whether your plan is too ambitious or not ambitious enough, rethinking the problem from the ground up, and producing structured deliverables that emphasize observability and diagrams.

When do I need to use a structured scope management process for my project?

Use structured scope management when you are asked to think bigger, need to decide whether to expand or reduce scope, or experience uncertainty about whether your plan achieves a 10-star outcome.

What deliverables should I expect from a rigorous product plan review?

Expect structured deliverables including observability expectations, error path mappings, diagrams, and written documentation of premises and failure modes that must be resolved before implementation proceeds.