plan-ceo-review

Pressure-test product plans with scope expansion, hold, or reduction modes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Founding teams struggle with under-validated plans, ambiguous scope, and risky tradeoffs that derail product initiatives. This skill provides a rigorous, founder-mode review process to surface key assumptions, enforce explicit decisions, and align leadership around a high-quality plan.

Core Features & Use Cases

  • Three-mode critique: SCOPE EXPANSION, HOLD SCOPE, and SCOPE REDUCTION to tailor ambition and risk.
  • Step zero system audit, edge-case mapping, and comprehensive risk/observability artifacts (ASCII diagrams, failure modes, runbooks).
  • Output-ready guidance for exec reviews, product planning, and roadmap alignment, including diagrams, risk logs, and actionable next steps.

Quick Start

Trigger this skill by selecting a mode and providing your plan details to begin a founder-level review.

Frequently Asked Questions about plan-ceo-review

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

FAQPage Schema
How do I pressure-test a product plan to identify risky tradeoffs?

Founder-mode plan review applies scope expansion, hold, or reduction modes to surface assumptions, map edge cases, and generate structured risk logs. This pressure-testing exposes risky tradeoffs and aligns leadership around a validated strategy.

What is the best way to perform a system audit before a roadmap planning session?

The best way to perform a system audit before roadmap planning is to execute a step-zero review that maps architecture via ASCII diagrams and identifies failure modes. This establishes rigorous baseline observability and risk awareness for feature scoping.

Can I use scope reduction to refine ambiguous feature scoping for an exec review?

Yes, you can use explicit scope reduction mode to refine ambiguous feature scoping. It enforces rigorous decision-making and generates output-ready runbooks and risk guidance specifically tailored for executive reviews and roadmap alignment.

How do you generate architecture diagrams and runbook guidance for product management?

You generate architecture diagrams and runbook guidance by enforcing ASCII diagram outputs during a step-zero system audit. This translates technical architecture and failure modes into structured, actionable artifacts for product management.

Does founder-level plan review support explicit mode selection for risk analysis?

Yes, founder-level plan review supports explicit mode selection including scope expansion, hold scope, and scope reduction. This tailors the depth of risk analysis and explicit decision-making to match your strategy review requirements.