# /plan-ceo-review: Review a plan for scope and ambition like a founder

Source: https://trendhub.net/skills/garrytan-gstack/plan-ceo-review
Skill folder: https://github.com/garrytan/gstack/tree/main/plan-ceo-review
Pack: gstack (https://trendhub.net/skills/garrytan-gstack)
Works with: Claude Code, Claude Code (team mode for a shared repo), Codex, Cursor, OpenCode, Gemini CLI and other agents

This review looks at a plan from the product owner's chair. It challenges the premise, maps reusable code, sketches the twelve-month ideal and recommends one of four modes, from scope expansion to reduction. Every addition or cut becomes a separate decision you approve, and the review then runs ten required sections covering errors, edge cases, observability and deployment.

## When to use it

- A feature plan feels too small or too safe and you want to see the bigger version.
- A plan has grown past what you can ship and needs cutting back.
- You want error paths, monitoring and rollback covered before engineering review.

## How it works

1. **Challenge the premise**: The agent names the real problem, the outcome and the cost of doing nothing, and checks whether the plan treats a proxy instead.
2. **Map existing code**: Each sub-problem is matched to code that already exists, and any rebuild must explain why refactoring is worse.
3. **Pick a mode**: Based on the plan's size and type it recommends expansion, selective expansion, hold or reduction, and you choose.
4. **Decide each change**: Proposed additions are offered one at a time to add, defer to TODOS.md or skip, and nothing is accepted silently.
5. **Run the review sections**: It works through the required sections, including an error and rescue map, failure modes and a test diagram.

## What it steers the agent away from

- Silent scope changes without your approval.
- Editing code during a plan review.
- Plans with catch-all error handling and no observability.

## What it can touch

Reads the repo and any design doc, and writes the reviewed plan, decision ledger and approved TODOs to files.

## Pairs well with

- `/autoplan`
- `/office-hours`
- `/plan-eng-review`

## Questions

### Will it rewrite my code?

No. It is review only and changes the plan document, not source files.

### How does it choose a mode?

It counts planned file changes and the kind of work, for example recommending reduction past fifteen changed files, but you make the final choice.
