plan-ceo-review

Review project plans through scope expansion, hold, or reduction modes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/yamparalarahul27/illu-ic --skill plan-ceo-review-yamparalarahul27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/yamparalarahul27/illu-ic/tree/main/.claude/skills/gstack/plan-ceo-review
Command: npx skills add https://github.com/yamparalarahul27/illu-ic --skill plan-ceo-review-yamparalarahul27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms a standard plan review into a high-stakes strategic session, ensuring that plans are not just feasible but extraordinary, catching critical flaws, and aligning with ambitious product visions.

Core Features & Use Cases

  • Strategic Scope Management: Guides users through three distinct review modes (Scope Expansion, Hold Scope, Scope Reduction) to tailor the review's ambition.
  • Deep Dive Analysis: Mandates rigorous examination of architecture, error handling, security, data flow, and long-term trajectory.
  • Use Case: A product manager submits a new feature plan. The AI, acting as a CEO, uses the 'Scope Expansion' mode to challenge assumptions, identify 10x opportunities, and ensure the plan aims for a 12-month ideal state, not just immediate delivery.

Quick Start

Use the plan-ceo-review skill to review the attached plan document in SCOPE EXPANSION 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 conduct a CEO-level review of a product strategy plan?

To conduct a CEO-level plan review, use a rigorous strategic planning process that challenges premises, evaluates risk assessment, and optimizes scope management to align project execution with long-term product visions.

What is strategic scope management in project plan reviews?

Strategic scope management in plan reviews involves evaluating a project through distinct modes: Scope Expansion to find 10x opportunities, Hold Scope to maintain current boundaries, and Scope Reduction to optimize resource allocation.

How do I use scope expansion to identify ambitious product opportunities?

Scope expansion challenges standard project assumptions by analyzing system architecture and data flow to push plans toward a 12-month ideal state, ensuring the final product strategy aims beyond immediate feature delivery.

Can a plan review assess long-term architecture and security trajectory?

Yes, a deep dive plan review mandates rigorous examination of system architecture, error handling, security protocols, and data flow to ensure the technical foundation supports the future ideal state of the product.

When do I need a rigorous plan review for my feature roadmap?

You need a rigorous plan review when transforming a standard feature roadmap into a high-stakes strategic session, ensuring the plan catches critical flaws and aligns technical execution with ambitious product visions.

What is the best way to challenge premises during strategic planning?

The best way to challenge premises during strategic planning is to analyze existing code leverage and system state, mandating a deep dive into data flow and long-term trajectory to catch critical flaws early.