plan-ceo-review

Audit product plans for assumptions, risks, and opportunity gaps.

2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/nicholaslocascio/x-claw-studio --skill plan-ceo-review-nicholaslocascio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/nicholaslocascio/x-claw-studio/tree/main/skills/gstack/plan-ceo-review
Command: npx skills add https://github.com/nicholaslocascio/x-claw-studio --skill plan-ceo-review-nicholaslocascio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit product plans with a rigorous CEO-style review framework that surfaces assumptions, risks, and opportunity gaps.

Core Features & Use Cases

  • Comprehensive framework including Step 0 nuclear scope, mode selection (SCOPE EXPANSION, HOLD SCOPE, SCOPE REDUCTION), and edge-case checks.
  • ASCII diagrams and structured outputs to document decision rationale and risk mapping.
  • Collaboration-friendly workflow with explicit decision points and traceable outputs.

Quick Start

Run the Mega Plan Review on your latest proposal to surface risks, dependencies, and edge cases.

Frequently Asked Questions about plan-ceo-review

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

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

A CEO-level plan review audits product plans to surface assumptions, risks, and opportunity gaps. It applies a rigorous framework to strategic plans, feature proposals, and roadmaps to ensure comprehensive scope evaluation.

What is scope reduction versus scope expansion in project plan evaluation?

Scope reduction and scope expansion are decision modes in project plan evaluation. Mode selection guides whether to expand, hold, or reduce scope based on surfaced risks, dependencies, and opportunity gaps during the audit.

How do I map risks and dependencies for architecture and governance decisions?

Mapping risks and dependencies for architecture and governance decisions requires structured outputs like risk-rescue maps and decision registers. These tools document rationale and ensure coverage of security, testing, and deployment concerns.

Can I use a structured audit framework to evaluate edge cases in strategic plans?

Yes, a structured audit framework evaluates edge cases in strategic plans by enforcing coverage of architecture, security, testing, deployment, and governance. It generates reproducible critique and traceable audit trails for decision-making.

What's the best way to document decision rationale and opportunity gaps in feature proposals?

The best way to document decision rationale and opportunity gaps in feature proposals is through structured outputs including ASCII diagrams and decision registers. This enables collaboration-friendly workflows with explicit decision points.

When should I not use a rigid plan evaluation framework for product management?

You should avoid a rigid plan evaluation framework when rapid prototyping requires immediate deployment without comprehensive architecture, security, or governance audits, as the structured process enforces strict scope and risk assessments.