plan-ceo-review

Guide CEO-level strategy reviews using a four-mode scope framework.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps founders and product leaders rethink problems, identify ambitious 10-star product directions, and surface scope changes to align teams and avoid under-scoped plans.

Core Features & Use Cases

  • Four operational modes (SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, SCOPE REDUCTION) to steer strategy reviews.
  • Proactive scenario analysis that surfaces bets, tradeoffs, risks, and edge cases during plan critique.
  • Applicable in CEO-level planning, roadmap sessions, and strategy discussions to push for higher impact.

Quick Start

Ask me to run a CEO-level plan review using the four-mode framework to think bigger and adjust scope accordingly.

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 to expand product scope?

A CEO-level plan review to expand product scope uses a four-mode framework—SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, and SCOPE REDUCTION—to rethink problems, surface ambitious directions, and adjust scope with guardrails. You select the appropriate mode and the framework guides the strategy critique.

What is the best way to surface risks and tradeoffs during a roadmap session?

The best way to surface risks and tradeoffs during a roadmap session is through proactive scenario analysis. This approach evaluates bets, identifies edge cases, and critiques the plan to align teams and avoid under-scoped product directions.

When do I need to use selective scope expansion for my product strategy?

You need selective scope expansion when a full scope expansion is too risky but holding scope limits growth. This mode targets specific ambitious product directions during a strategy critique, allowing targeted growth while maintaining guardrails on the broader roadmap.

Can I use this plan review framework for startup risk reassessment?

Yes, you can use this plan review framework for startup risk reassessment. It applies to CEO-level planning and strategy discussions across startups, helping founders rethink problems, evaluate bets, and surface necessary scope changes to avoid under-scoped plans.

How do I decide between holding scope and scope reduction in strategy critiques?

Deciding between holding scope and scope reduction depends on risk levels and growth capacity. HOLD SCOPE maintains current trajectory, while SCOPE REDUCTION narrows focus to mitigate identified risks; both modes enforce guardrails to align teams during the plan review.