plan-ceo-review

Coordinate a CEO-level review of project plans to surface risks and scope gaps.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/EhsaanArk/ai-signal-router --skill plan-ceo-review-ehsaanark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/EhsaanArk/ai-signal-router/tree/main/.claude/skills/gstack/plan-ceo-review
Command: npx skills add https://github.com/EhsaanArk/ai-signal-router --skill plan-ceo-review-ehsaanark

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, CEO-level critique of project plans to surface strategy misalignments, missing risks, and scope gaps before execution, reducing the chance of costly pivots later.

Core Features & Use Cases

  • Structured CEO-review workflow: enforces a disciplined evaluation of problem statements, design tradeoffs, and resource implications.
  • Artifact-aware checks: validates the presence and quality of design docs, TODOS, handoff notes, and supporting materials.
  • Escalation & governance: integrates decision gates, risk flags, and stakeholder notifications to accelerate alignment.
  • Telemetry & audit trail: records review outcomes for accountability and continuous improvement.

Quick Start

Invoke /plan-ceo-review to start an in-depth CEO-level plan appraisal for your current feature branch.

Frequently Asked Questions about plan-ceo-review

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

FAQPage Schema
How do I conduct a structured CEO-level plan review for a feature proposal?

A structured plan review evaluates problem statements, design tradeoffs, and resource implications to surface strategy misalignments and scope gaps. This process enforces a disciplined appraisal of project plans before execution to reduce costly pivots.

What is the best way to assess risks and scope gaps in a software design doc before execution?

Assessing risks and scope gaps requires a rigorous critique of design docs to identify missing risks and strategic misalignments. Applying artifact-aware checks validates the presence and quality of supporting materials like TODOS and handoff notes.

Can I use this plan review process for architecture and PR plans across different domains?

Yes, this plan review process applies to feature proposals and PR plans across software, design, and architecture. It evaluates risk assessment, scope decisions, and long-term impact wherever these factors matter.

How does telemetry logging track plan review outcomes and governance decisions?

Telemetry logging records review outcomes by integrating decision gates, risk flags, and stakeholder notifications. This creates an audit trail for accountability and continuous improvement of the evaluation process.

Do I need design docs and handoff notes to perform an artifact-aware plan appraisal?

Yes, design docs, TODOS, and handoff notes are required inputs for artifact-aware checks. The review validates the presence and quality of these supporting materials to ensure complete project governance.

When should I not use a CEO-level plan review workflow?

A CEO-level plan review is not suited for rapid, low-risk tasks lacking strategic or long-term impact. It is designed for complex plans where risk assessment, scope decisions, and resource implications demand structured escalation handling.