plan-ceo-review

Challenges plan scope, risks, and execution path with governance checks.

Updated Oct 25, 2025
One-click install
npx skills add https://github.com/shaythegay13/serenity-pocket-app-final --skill plan-ceo-review-shaythegay13
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/shaythegay13/serenity-pocket-app-final/tree/main/.claude/skills/gstack/plan-ceo-review
Command: npx skills add https://github.com/shaythegay13/serenity-pocket-app-final --skill plan-ceo-review-shaythegay13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, CEO-grade review workflow that rigorously challenges plan scope, assumptions, and execution risks to prevent scope creep and misaligned bets.

Core Features & Use Cases

  • Multi-mode review: SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, and SCOPE REDUCTION to shape the plan toward ambitious but achievable outcomes.
  • Front-loaded governance: mandatory Step 0 system audit, design-doc alignment checks, risk and failure-mode mapping, and a clear plan-status workflow to surface gaps before execution.
  • Collaboration enablement: integrates handoff notes, design decisions, and design-doc checks to align product, engineering, and business stakeholders.

Quick Start

Start by running this skill against your plan to trigger a rigorous, expansion-ready CEO-level evaluation.

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 strategic plan for scope creep and execution risks?▼

Review a strategic plan for scope creep by applying a CEO-grade evaluation that challenges scope, assumptions, and failure modes. This governance workflow enforces a Step 0 system audit and design-doc checks to surface gaps before execution.

What is the best way to align product and engineering stakeholders before plan execution?▼

Align product and engineering stakeholders by integrating handoff notes, design decisions, and design-doc checks within the plan review. This formal plan-status workflow ensures completeness and collaboration across business goals.

How do I decide between scope expansion and scope reduction for a strategic plan?▼

Decide between scope expansion and reduction by using a multi-mode review process. It evaluates whether a plan requires expansion, selective expansion, holding scope, or reduction to shape outcomes toward ambitious but achievable goals.

Does this plan review process require a preliminary system audit?▼

Yes, this plan review process requires a mandatory Step 0 system audit. Front-loaded governance enforces this preliminary audit alongside risk and failure-mode mapping to ensure precise scoping decisions before execution.

How do I map failure modes and risks in a design document?▼

Map failure modes and risks in a design document by applying a formal CEO-level evaluation. The review enforces risk mapping and design-doc alignment checks to prevent misaligned bets and identify execution path vulnerabilities.

When should I not use an automated plan review workflow?▼

You should not use an automated plan review workflow for tactical tasks lacking strategic business goals or design documents. The process requires multi-mode scoping decisions and a Step 0 system audit to properly evaluate execution risks.