plan-ceo-review

Review CEO-level plans for scope, risks, and execution readiness.

107|19|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/mr-daedalium/ostack --skill plan-ceo-review-mr-daedalium
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/mr-daedalium/ostack/tree/main/plan-ceo-review
Command: npx skills add https://github.com/mr-daedalium/ostack --skill plan-ceo-review-mr-daedalium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, high-signal plan review workflow that challenges assumptions, expands or tightens scope, and surfaces risks to deliver a stronger, execution-ready plan.

Core Features & Use Cases

  • Premise Challenge: systematically interrogates the problem statement and premises to ensure alignment with user goals.
  • Mode-based Planning: supports SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, and SCOPE REDUCTION to tailor the review depth.
  • Handoff & Design Alignment: checks for design-doc coherence, design handoffs, and prerequisites like design artifacts or office-hours inputs.
  • Operational Readiness: validates dependencies, risk mitigations, escalation paths, and observability requirements to enable safe deployment.
  • Use Case: a product plan for a new feature is reviewed to ensure scope is ambitious but feasible, with explicit success criteria and rollout plan.

Quick Start

Review the current product plan for CEO readiness and adjust scope to maximize impact.

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 product plan for CEO readiness and strategic risks?

Reviewing a product plan for CEO readiness involves rigorously interrogating premises, validating scope against execution risks, and ensuring design-doc alignment. This process challenges assumptions to deliver a stronger, execution-ready plan with explicit escalation paths.

What is the best way to challenge assumptions during a strategic plan review?

Challenging assumptions during a strategic plan review requires systematically interrogating the problem statement and premises. This ensures the plan aligns with user goals while expanding or tightening scope to maximize impact and surface hidden risks.

Can I adjust scope expansion depth when evaluating a CEO-level product plan?

You can adjust scope evaluation depth using mode-based planning. The review supports scope expansion, selective expansion, hold scope, and scope reduction to tailor the strategic deep dive and ensure the plan is ambitious but feasible.

How do I ensure operational readiness and risk mitigation before a feature rollout?

Ensuring operational readiness requires validating dependencies, risk mitigations, and escalation paths. The plan review checks for observability requirements and rollout plans to enable safe deployment and comprehensive risk-resilience.

What prerequisites do I need for a design doc coherence check during plan review?

Prerequisites for a design doc coherence check include having design artifacts and office-hours inputs ready. The review validates these prerequisites to ensure proper design handoffs and alignment before escalating the plan for approval.