plan-ceo-review

Review product plans with CEO-level scope and risk assessment modes.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/hetsheth-droid/toolbox-template --skill plan-ceo-review-hetsheth-droid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/hetsheth-droid/toolbox-template/tree/main/incubating/gstack/plan-ceo-review
Command: npx skills add https://github.com/hetsheth-droid/toolbox-template --skill plan-ceo-review-hetsheth-droid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured framework to critique and improve product plans at the CEO/founder level, surfacing misaligned assumptions and guiding scope decisions.

Core Features & Use Cases

  • Four modes: SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, and SCOPE REDUCTION to tailor the plan to ambition and risk.
  • Guided decision prompts and traceable documentation to capture rationale, risks, and tradeoffs.
  • Use Case: during a strategy sprint, challenge a proposed roadmap to ensure it delivers real user value without unnecessary bloat.

Quick Start

Initiate plan-ceo-review to start a structured evaluation of your current plan.

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 challenge product scope and align strategy?

A plan review evaluates your product strategy by challenging scope assumptions and aligning them with user outcomes. It uses structured decision paths and traceable documentation to capture risks, tradeoffs, and milestone testability.

What is the best way to assess risk and scope expansion during a strategy sprint?

Risk assessment during a strategy sprint uses four modes: scope expansion, selective expansion, hold scope, and scope reduction. These modes tailor your roadmap evaluation to match your ambition while surfacing misaligned assumptions.

How do I document decision rationale and tradeoffs when reducing product scope?

Scope reduction documentation requires guided decision prompts that capture explicit rationale, risks, and tradeoffs. This creates traceable records linking scope decisions directly to user outcomes and strategic alignment.

When do I need explicit edge-case coverage and testable milestones for plan evaluation?

Explicit edge-case coverage and testable milestones are required for both early ideation and later-stage strategy reviews. They ensure your plan delivers real user value without unnecessary bloat and maintain clear decision paths.

Can I use structured plan reviews for both early ideation and later-stage strategy assessment?

Yes, structured plan reviews apply to both early ideation and later-stage strategy. They handle expansion, reduction, and risk assessment scenarios while requiring explicit edge-case coverage and clear decision paths with documentation.

Why does plan review require traceable documentation and clear decision paths?

Traceable documentation and clear decision paths are required to capture the rationale behind scope decisions. They surface misaligned assumptions and ensure every tradeoff is linked to testable milestones and user outcomes.