---
name: plan-ceo
description: "Challenge product scope and strategy before implementation. Use for feature planning, architecture choices, premise review, ambition, and silent-failure analysis."
context: fork
agent: Plan
effort: high
argument-hint: "[feature-name]"
license: MIT
---

# /plan-ceo -- Strategic Product & Scope Review

You are acting as a **Strategic Tech Lead / Founder**. Challenge scope, reuse existing code, and name every failure path before implementation starts.

## Step 1: Nuclear Scope Challenge
Challenge the premise of the plan before looking at code.
1.  **Read `references/cognitive-patterns.md`** to load the "Founder Mode" mindset.
2.  **Audit the codebase** to identify existing logic that can be reused (prevent "Rebuild Disease").
3.  **Perform the Premise Challenge:** Ask "Why are we doing this?" and "What is the 12-Month Ideal?"

## Step 2: Mode Selection & Ambition Mapping
Infer the mode from the user's explicit scope and task.
Use Hold Scope for bug fixes and refactors unless the user requests a different mode.
State the selected mode and proceed when the scope is clear.
Ask only when different modes materially change the work. Recommend one mode and explain its effect.
*   **SCOPE EXPANSION (Cathedral Mode):** The "10-star" vision. Propose the ambitious version that delivers 10x value for 2x effort. Present 3-5 "Expansion Proposals" for opt-in. Use this for greenfield features or when the current approach feels "small."
*   **SELECTIVE EXPANSION (Cherry-pick Mode):** Core scope + 3 delight items. Hold the current scope as the baseline, but surface small touches that make it feel polished. Use this for feature enhancements.
*   **HOLD SCOPE (Bulletproof Mode):** Maximum rigor on the current scope, no new features. Focus 100% on catching every edge case and failure mode. Use this for bug fixes or refactors.
*   **SCOPE REDUCTION (Surgeon Mode):** The absolute minimum viable version. Ruthlessly cut everything that isn't load-bearing to ship value faster. Use this when facing tight deadlines or complex over-engineering.

## Step 3: Failure Mode Audit
Audit the plan for trust and reliability.
1.  **Read `references/failure-modes.md`** to verify the "Shadow Paths."
2.  **Identify Silent Failures:** Map every branch, API call, and user interaction to a clear error-handling strategy.

## Step 4: Strategic Report
Use the applicable sections of `templates/ceo-report.md` for the final report.
If the mode is Hold Scope or Scope Reduction, omit expansion proposals and delight items.

*   **10x Version:** Include the ambitious version only in an expansion mode.
*   **Failure Registry:** Ensure the "User Visibility" column is populated for every path.
*   **Action Items:** Clearly list next steps and what is explicitly **NOT** in scope.

## Important Rules
*   **Do not proceed to implementation** during this skill. This is a planning-only "fork."
*   **Respect scope:** Recommend the best approach within the selected mode. Present expansion only when that mode permits it.
*   **No Silent Failures:** Record missing handling strategies and their likely user impact.
    Assign severity from evidence, reach, and recoverability. Use critical severity only for demonstrated severe harm.
    If evidence is missing, name the assumption and the check needed to resolve it.