plan-ceo-review

Coordinate CEO-review planning with mode selection and risk mapping.

55|8|Updated Jul 21, 2021

Search Tags:#planning #strategy #product-management #risk-analysis #review-process #ceo-review

Ready to run

npx skills add https://github.com/Actual-Chat/actual-chat --skill plan-ceo-review-actual-chat

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/Actual-Chat/actual-chat/tree/main/.claude/skills/plan-ceo-review
Command: npx skills add https://github.com/Actual-Chat/actual-chat --skill plan-ceo-review-actual-chat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CEO/founder-mode plan reviews are time-consuming and error-prone without a structured framework. This skill guides teams through rigorous evaluation of proposals, tradeoffs, and execution risks.

Core Features & Use Cases

Structured mode selection: SCOPE EXPANSION, HOLD SCOPE, SCOPE REDUCTION to align scope with business value.
Risk and rescue mapping: formalized handling of failure modes, dependencies, and decision logs.
Decision documentation: traceable records of base assumptions, decision criteria, and next steps for leadership review.

Quick Start

Choose a target initiative, select a mode, and generate a structured plan for leadership 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 structure a CEO review for strategic product initiatives?▼

Plan CEO reviews by selecting a strategic scope mode—expansion, hold, or reduction—and mapping explicit risk and rescue paths. This structured workflow generates decision logs that document base assumptions and execution risks for leadership evaluation.

What is scope mode selection in product strategy reviews?▼

Scope mode selection aligns product scope with business value by choosing between scope expansion, hold scope, or scope reduction. It forces explicit tradeoffs during strategic reviews, ensuring leadership evaluates whether to grow, maintain, or cut initiative boundaries.

How do I document tradeoffs and assumptions for founder-mode plan reviews?▼

Document tradeoffs and assumptions by generating traceable decision logs during the review workflow. These records capture base assumptions, decision criteria, failure modes, and next steps, providing a clear audit trail for leadership to evaluate strategic proposals.

Can I use this review process to prevent silent failures in product management?▼

Yes, the review process prevents silent failures through formalized risk and rescue mapping. By explicitly mapping failure modes and dependencies alongside decision logs, teams ensure execution risks are visible and addressed before leadership approval.

When do I need formal risk and rescue mapping for a product strategy review?▼

You need formal risk and rescue mapping when evaluating strategic product initiatives that require careful tradeoffs. It is essential for identifying failure modes and dependencies during scope expansion, holds, or reductions to prevent silent failures in execution.