Review plan

/ogre:review-plan

Use this skill after an execution plan exists and before implementation starts.

Inputs

Accept:

• Issue number, e.g. 107
• Plan name, e.g. issue-107
• Plan path, e.g. .ai/.ogre/plans/issue-107.md

Optional flags:

• --reviewer claude|codex
• --model MODEL
• --reasoning LEVEL (reasoning effort for the reviewer; omit to use the CLI's own default)
• --main — run the review inline in this session instead of spawning an isolated subprocess (loses context isolation; only pass when the user explicitly wants that).
• --background — spawn the isolated subprocess detached; returns immediately instead of waiting for the review to finish.
• --live — opt-in, off by default. Runs the reviewer with --json/--output-format stream-json --verbose instead of plain text, writing raw JSONL to the log path. Only use when the user explicitly wants to watch the review happen live — see /ogre:rescue's "Watching a --live rescue live" section for the Monitor+jq recipe (same recipe, against review-plan's own log path).

Flags are forwarded verbatim, never reinterpreted. -r is --reviewer and -R is --reasoning (reviewer got the lowercase letter since it's the one used regularly - this was previously swapped, a real bug, fixed). -m/-M (--model/--main) still differ only by case with unrelated meanings, so a wrong guess there is silent (no parse error, just wrong behavior). If the user's own message names an actual flag/short-form, pass that exact token through unchanged rather than guessing a different one you assume is equivalent.

Behavior

Hard requirement, every completion message this skill produces, no exception: must literally contain Job Id:, Issue: (number + name), Review: (the .ai/.ogre/reviews/issue-<number>/plan-review.md path), and Steps: (step count of the plan being reviewed) lines with their real values. A terse summary sentence is fine, even under caveman/ultra/terse mode — but it must not be the only thing shown; the Job Id:/Issue:/Review:/Steps: lines still have to appear alongside it, every time.

1. Run:
   • ${CLAUDE_PLUGIN_ROOT}/scripts/ogre review-plan <issue-or-plan> [flags]
2. By default the helper spawns an isolated reviewer subprocess itself and the ogre review-plan call blocks until it finishes (same isolation model as ogre execute) - you do not read the runner or perform the review yourself. Never invoke it as a plain synchronous Bash call - always wrap it in one single Bash tool call with run_in_background: true around that same command, even though it's usually a single quick review. This keeps the main conversation free the whole run and makes it visible in /tasks instead of hard-blocking the turn. The harness delivers one completion notification straight to this session the moment the command exits - read its "Task ... finished: passed|failed" line from that output. Do not poll for this case; the notification itself is the signal. If --live was used and a Monitor is armed on the log path, TaskStop it right here, before reporting - tail -f never exits on its own, so it stays open in the TUI until timeout or a manual (x) if you don't.
   • Pass --background to spawn detached and return immediately (this quick returning call doesn't itself need the run_in_background wrapper) - report the task id to the user, then immediately start a poll loop yourself in this same session: one single Bash tool call with run_in_background: true around a real shell loop, e.g. while :; do ${CLAUDE_PLUGIN_ROOT}/scripts/ogre status --task <tid> | grep -qE '^\| Status +\| (passed|failed) ' && break; sleep 20; done. The harness delivers a completion notification straight to this session the moment that loop exits - read the final ogre status --task <tid> output and report pass/fail to the user then. Never poll across separate assistant turns, and never hand this off to a fork/subagent (a fork always burns Claude quota regardless of which reviewer executor was used, for zero benefit - the background subprocess already does all the work itself). If --live was used and a Monitor is armed on the log path, TaskStop it right here, before reporting - tail -f never exits on its own, so it stays open in the TUI until timeout or a manual (x) if you don't.
   • Pass --main only if the user explicitly wants the review done inline in this session (spends this session's own context, loses isolation) - in that case, and only then, read .ai/.ogre/tmp/issue-<number>/plan-review-runner.md yourself: if reviewer is claude, perform the review directly; if reviewer is codex, either use codex exec -m MODEL -c model_reasoning_effort=LEVEL - < runner (omit -c model_reasoning_effort=... if the user gave no --reasoning), or ask the user to run it through codex-plugin-cc if they prefer same Claude Code TUI. Write output to .ai/.ogre/reviews/issue-<number>/plan-review.md.
3. If the run failed (or --background is still running), do not treat the review as ready - check .ai/.ogre/logs/issue-<number>/ for the reviewer's own log before deciding what to do next.
4. Do not edit code.
5. Do not rewrite the plan unless the user explicitly asks.

Review Focus

Find:

• Hallucinated files/classes/routes/tables/columns/methods/config keys/package APIs.
• Missing validation steps.
• Risky assumptions.
• Over-scoped work.
• Steps that should be split smaller.
• Blocker dependency problems.
• NEEDS INSPECTION items that should block execution.

Output

Use the plan review format from:

• .ai/.ogre/prompts/plan-review-prompt.md