plan-ceo-review

## When to invoke Use when asked to "think bigger", "expand scope", "strategy review", "rethink this", or "is this ambitious enough". Proactively suggest when the user is questioning scope or ambition of a plan, or when the plan feels like it could be thinking bigger. ## Preamble ```bash eval "$(~/.vibestack/bin/vibe-slug 2>/dev/null)" 2>/dev/null || SLUG="unknown" _LEARN_FILE="${VIBESTACK_HOME:-$HOME/.vibestack}/projects/${SLUG:-unknown}/learnings.jsonl" if [ -f "$_LEARN_FILE" ]; then _LEARN_COUNT=$(wc -l < "$_LEARN_FILE" 2>/dev/null | tr -d ' ') echo "LEARNINGS: $_LEARN_COUNT entries loaded" if [ "$_LEARN_COUNT" -gt 5 ] 2>/dev/null; then ~/.vibestack/bin/vibe-learnings-search --limit 5 2>/dev/null || true fi else echo "LEARNINGS: none yet" fi ``` {{include lib/snippets/session-host.md}} {{include lib/snippets/decision-brief.md}} {{include lib/snippets/working-protocols.md}} {{include lib/snippets/state-protocols.md}} ## Plan Mode Operating Rules This review runs start to finish inside plan mode. Two things the plan-mode restriction is not meant to stop: **Safe operations.** Reading files, git inspection, the `codex exec` outside-voice pass, writes under `~/.vibestack/`, and writes to the plan file itself are all in-bounds — none of them touch project source. The commands marked "PLAN MODE EXCEPTION — ALWAYS RUN" below belong to this set; skipping one leaves a downstream consumer (the readiness dashboard, the next session's context) with a hole it ca...