plan-ceo-review

Enforce a structured CEO review workflow for strategic plans.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill plan-ceo-review-jm199seo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/jm199seo/lostark-accessory-viewer/tree/main/.claude/skills/gstack/plan-ceo-review
Command: npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill plan-ceo-review-jm199seo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Plan CEO Review provides a rigorous, repeatable process to scrutinize and improve strategic plans before a CEO-level review. It enforces a Step 0 system audit, alignment with design docs and handoff notes, and explicit mode choices to expand, constrain, or refine scope.

Core Features & Use Cases

  • Step 0 system audit and design-doc alignment to ground the problem, constraints, and proposed approach.
  • Mode-driven scope decisions (SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, SCOPE REDUCTION) to balance ambition and rigor.
  • Handoff notes, design-doc handoffs, and telemetry for traceability and continuous improvement.

Quick Start

Start the review by running the Plan CEO Review workflow on the current branch to trigger the system audit and scope 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 prepare a strategic plan for a CEO review?

Prepare a strategic plan for a CEO review by enforcing a structured workflow that includes a Step 0 system audit, design-doc alignment, and explicit scope mode decisions. This process grounds problem framing, validates constraints, and balances ambition with rigor before executive scrutiny.

What is a Step 0 system audit in product plan evaluation?

A Step 0 system audit in product plan evaluation is a pre-review protocol that aligns the proposed approach with existing design docs and handoff notes. It grounds the problem framing and constraints to ensure the strategic plan is rigorous before reaching executive review.

How do I manage scope decisions during a design-doc alignment?

Manage scope decisions during a design-doc alignment by applying mode-driven choices like scope expansion, selective expansion, hold scope, or scope reduction. This formal protocol balances engineering and UX ambition with project rigor during the plan review process.

How does handoff telemetry improve strategic plan reviews?

Handoff telemetry improves strategic plan reviews by capturing formal completion status and handoff context artifacts. This establishes traceability across product and engineering teams, enabling continuous improvement and tracking of executive review outcomes.

Can I use this structured review workflow for engineering and UX handoffs?

Yes, you can use this structured review workflow for engineering and UX handoffs. It explicitly captures handoff notes and design-doc alignments across product, engineering, and UX teams to ensure traceability and validate scope decisions during the CEO review.

When should I use mode-based scope reduction in a plan review?

Use mode-based scope reduction in a plan review when the Step 0 system audit or design-doc alignment reveals constraints that require narrowing ambition. This mode decision ensures the strategic plan remains viable and rigorous for the final CEO review.