meow:plan-ceo-review

Reviews plans via CEO-level workflow with Premise Challenge, Scope Decision, Analysis phases.

14|2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-plan-ceo-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meow:plan-ceo-review
Source: https://github.com/ngocsangyem/MeowKit/tree/main/.claude/skills/meow%3Aplan-ceo-review
Command: npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-plan-ceo-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Performs rigorous CEO-level plan reviews to validate ambitious yet feasible strategy by applying four modes (Expansion, Selective Expansion, Hold Scope, Scope Reduction) and a structured review workflow.

Core Features & Use Cases

  • Structured, multi-stage evaluation of plans with premise challenges, scope decisions, and mode-specific analyses to surface risks and opportunities.
  • Handoff-ready outputs, references, and diagrams to align stakeholders and ensure traceability.
  • Plan persistence and versioning to maintain a living record of decisions and future review readiness.

Quick Start

Run /meow:plan-ceo-review to start the CEO plan review workflow.

Frequently Asked Questions about meow:plan-ceo-review

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

FAQPage Schema
How do I conduct a CEO-level plan review for a high-stakes product initiative?

A CEO plan review validates ambitious strategy and ensures feasible scope through a structured workflow, applying four modes: Expansion, Selective Expansion, Hold Scope, and Scope Reduction to guide scope decisions and risk assessment.

What is the best way to assess risk and scope feasibility for an ambitious product strategy?

Risk assessment and scope feasibility are evaluated through multi-stage premise challenges and mode-specific analyses. This structured review process surfaces hidden risks and opportunities to align stakeholders on feasible scope decisions.

How does plan persistence and versioning work for strategy reviews?

Plan persistence and versioning maintain a living record of decisions through mandatory frontmatter, references, and plan-logging artifacts. This enables traceability, governance, and future review readiness across high-stakes product initiatives.

Can I generate handoff-ready outputs with diagrams for stakeholder alignment?

Yes, the review workflow generates handoff-ready outputs, references, and diagrams to align stakeholders. These artifacts ensure traceability and governance for high-stakes product initiatives throughout the scope decision process.

When should I use scope reduction mode versus expansion mode in a plan review?

Scope reduction mode applies when feasible scope must contract to manage risk, while expansion mode validates ambitious strategy growth. Selective expansion and hold scope modes address intermediate scenarios in high-stakes product initiatives.

What artifacts are required for traceability and governance in strategy plan reviews?

Mandatory frontmatter, references, diagrams, and plan-logging artifacts enforce traceability and governance. These structured outputs maintain a living record of decisions and ensure future review readiness for ambitious product strategies.