plan-ceo-review

Review strategy proposals with CEO-style risk-aware plan critiques.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a rigorous framework for conducting CEO-style reviews of strategic plans, ensuring completeness, risk-awareness, and clear handoffs.

Core Features & Use Cases

  • Structured Step 0 system audit and premise challenge to surface design flaws early.
  • Handoff and mid-session context capture to preserve continuity across sessions.
  • Enforced use of frontmatter design docs, handoff notes, and telemetry-friendly reporting.
  • Flexible modes (SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, SCOPE REDUCTION) to shape the review.
  • Built-in escalation, risk mapping, and failure-mode identification to improve plan quality.

Quick Start

Start by running /plan-ceo-review on your current feature branch to trigger a comprehensive plan critique.

Frequently Asked Questions about plan-ceo-review

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

FAQPage Schema
How do I perform a CEO-style plan review on a new strategy proposal?

A CEO-style plan review audits strategic proposals for completeness and risk-awareness by applying structured premise challenges, design-doc checks, and failure-mode identification. This enforces frontmatter extraction and generates telemetry-friendly reports with handoff notes.

What is the best way to ensure strategic plan completeness before a high-stakes pitch?

Ensuring strategic plan completeness requires a rigorous Step 0 system audit and premise challenge to surface design flaws early. This enforces structured frontmatter extraction and edge-case handling to guarantee high-stakes roadmaps and funding pitches are defensible.

Can I use a design-doc framework to manage risk and escalation paths for product roadmaps?

Yes, using a design-doc framework for product roadmaps enables built-in risk mapping and escalation path identification. It captures mid-session context to preserve continuity and ensures strategy adjustments are tracked via telemetry-friendly reporting.

Does this plan review approach support scope adjustment during roadmap evaluation?

Yes, this plan review approach supports scope adjustment during roadmap evaluation through flexible modes including SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, and SCOPE REDUCTION. These modes shape the critique to fit specific growth strategies and constraints.

How do I maintain context continuity across multiple strategy plan review sessions?

Maintaining context continuity across strategy plan review sessions requires structured handoff and mid-session context capture mechanisms. This preserves continuity by enforcing the use of handoff notes and telemetry data directly within the design-doc frontmatter.

When do I need a formal risk-aware critique framework for business plans?

You need a formal risk-aware critique framework for business plans when dealing with high-stakes growth strategies, funding pitches, and roadmaps where defensibility matters. It enforces edge-case handling and structured reporting to prevent critical design flaws.