ceo-review

Audit plans, specs, or context packets with premise challenge and alternatives.

2|Updated Oct 2, 2025
One-click install
npx skills add https://github.com/misty-step/volume --skill ceo-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ceo-review
Source: https://github.com/misty-step/volume/tree/main/.agents/skills/ceo-review
Command: npx skills add https://github.com/misty-step/volume --skill ceo-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dialectical premise-and-alternatives audit for a plan, spec, or context packet. Four moves: premise challenge (is this the right problem?), mandatory structurally-distinct alternatives, cross-model outside voice, user-ratified convergence. Named for Gary Tan's plan-ceo-review pattern; operationalizes the AGENTS.md "Diverge Before You Converge" doctrine at the plan-review stage. Use when: about to commit to a plan/spec/design, reviewing a ticket before shape, when "is this the right problem" would be useful, or any time a proposal smells like a symptom fix instead of a root-cause fix. Trigger: /ceo-review, /challenge, /premise-check. argument-hint: "[plan|spec|context-packet|ticket]"

Core Features & Use Cases

  • Premise Challenge: Probes the problem statement to confirm the actual user outcome.
  • Mandatory Alternatives: Produces ≥2 structurally distinct approaches with load-bearing assumptions.
  • Outside Voice: Invokes an independent cross-model or external perspective to critique framing.
  • Ratification: Delivers a concrete recommendation and next steps for execution.

Quick Start

Invoke /ceo-review on your plan, spec, or context packet to begin the audit.

Frequently Asked Questions about ceo-review

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

FAQPage Schema
How do I challenge plan premises to ensure I am fixing the root cause and not just a symptom?

A dialectical plan review audits your plan by enforcing premise challenge, mandatory structurally-distinct alternatives, and an outside voice critique. This structured audit surfaces misalignments and prevents you from committing to a flawed problem statement or design.

What is the best way to generate structurally distinct alternatives before committing to a spec?

A mandatory alternatives review forces the generation of at least two structurally distinct approaches alongside their load-bearing assumptions. This process ensures you evaluate fundamentally different execution paths rather than minor variations before finalizing a design.

Can I use a dialectical review to audit a ticket before shaping it into a full plan?

Yes, you can apply a dialectical ticket review to evaluate proposed changes before shaping them into a full plan. This audit probes whether the ticket addresses the actual user outcome, preventing premature commitment to a flawed problem framing.

How does an outside voice critique help evaluate proposed changes in a plan review?

An outside voice critique invokes an independent cross-model perspective to critique the framing of your plan or context packet. This external perspective identifies structural flaws and blind spots that internal reviewers might miss during the convergence phase.

When should I not use a premise challenge audit for my proposal?

You should avoid a premise challenge audit when a plan is already ratified and in active execution, or when the problem framing is trivially clear. This dialectical audit is designed for the pre-commitment stage to surface misalignments before allocating resources.