plan-ceo-review

Reviews implementation plans with CEO-level scope, strategy, and failure-mode analysis.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans often ship with unchallenged assumptions, hidden failure modes, and scope that is either too timid or too bloated. This Skill applies a founder-mode review to any plan before implementation, catching landmines early and forcing explicit scope decisions. ## Core Features & Use Cases - Four Review Modes: SCOPE EXPANSION (dream bigger), SELECTIVE EXPANSION (hold scope, cherry-pick expansions), HOLD SCOPE (maximum rigor), and SCOPE REDUCTION (strip to essentials), each chosen explicitly by the user. - Failure-Mode Auditing: Maps error paths, silent failures, edge cases, and shadow data flows, and requires diagrams, observability, and test coverage as first-class plan deliverables. - Structured Decision Flow: Every scope change is presented as an explicit opt-in question with completeness scores and effort estimates, keeping the user in control. - Use Case: Before implementing a new company-invitation flow, run this review to challenge whether the plan handles invite expiry, duplicate joins, and rollback, and to decide whether the scope is ambitious enough. ## Quick Start Ask the assistant to run a CEO review on the current plan and choose whether to expand, hold, or reduce its scope.

Frequently Asked Questions about plan-ceo-review

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

FAQPage Schema
How do I review a plan before implementing it?

Invoke the plan-ceo-review skill on your plan and pick one of four modes: scope expansion, selective expansion, hold scope, or scope reduction. The review then audits failure modes, edge cases, tests, and observability, presenting every scope change as an explicit opt-in decision.

What is the difference between scope expansion and selective expansion?

Scope expansion rethinks the problem and pushes scope up toward the ideal product. Selective expansion holds the current scope as the baseline but surfaces each expansion opportunity individually so you can cherry-pick which ones to accept.

Does this skill make code changes during the review?

No. The skill explicitly forbids code changes and implementation. Its only job is to review the plan with rigor, present decisions, and record accepted or rejected scope items.

When should I use scope reduction mode?

Use scope reduction when a plan is bloated or timeline pressure is high. It acts like a surgeon, finding the minimum viable version that achieves the core outcome and cutting everything else.

What tools does the plan review skill require?

It uses Read, Grep, Glob, Bash, AskUserQuestion, and WebSearch. It also detects the git hosting platform and base branch using gh, glab, or git-native fallback commands.