plan-ceo-review

Review strategic plans and product roadmaps across multiple review modes.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/kitfunso/omniskill --skill plan-ceo-review-kitfunso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/kitfunso/omniskill/tree/main/skills/plan-ceo-review
Command: npx skills add https://github.com/kitfunso/omniskill --skill plan-ceo-review-kitfunso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This suite provides rigorous, multi‑mode plan reviews for complex initiatives, surfacing assumptions, trade‑offs, and risks early to guide better decision‑making and alignment across teams.

Core Features & Use Cases

  • Systematic pre‑review with a project/system audit, design‑doc checks, and TODOS mapping.
  • Multi‑mode review workflow (SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, SCOPE REDUCTION) with explicit opt‑in via AskUserQuestion.
  • Comprehensive risk and completeness scaffolding: premise challenges, implementation alternatives, and escalation paths, plus telemetry to track outcomes.

Quick Start

Begin Step 0 by challenging the premise, mapping options, and selecting a mode, then execute the chosen plan.

Frequently Asked Questions about plan-ceo-review

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

FAQPage Schema
How do I perform a rigorous plan review for a complex strategic initiative?

A rigorous plan review systematically audits project premises, maps implementation alternatives, and challenges core assumptions to surface risks and trade-offs early. This ensures better strategic alignment and decision-making before execution begins.

What is multi-mode scope analysis for product roadmaps?

Multi-mode scope analysis evaluates a product roadmap by applying criteria for scope expansion, selective expansion, hold scope, or scope reduction. It uses an explicit opt-in workflow to guide resource allocation and risk management across teams.

How do I challenge design doc assumptions and map architectural risks?

Challenging design doc assumptions requires a pre-review process that audits the system, checks documentation completeness, and maps TODOS. This scaffolding surfaces hidden implementation risks and establishes clear escalation paths for architecture reviews.

Can I use telemetry to track outcomes of a strategic plan review?

Telemetry tracks strategic plan review outcomes by capturing mode selection, premise challenge results, and risk-mapping data. This ensures completeness and provides measurable feedback to guide multi-team alignment and future decision-making.

When do I need a formal pre-review audit for a feature proposal?

A formal pre-review audit is needed for feature proposals when you must surface trade-offs across multiple teams, map implementation alternatives, and establish risk scaffolding before committing to a specific execution mode.