← ClaudeAtlas

review-planlisted

Review an Ogre execution plan against the repository for hallucinations, risky assumptions, missing validation, and over-scoped steps.
metallurgical/ogre-runner · ★ 1 · Code & Development · score 59
Install: claude install-skill metallurgical/ogre-runner
# /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` — omitted, this falls back to `defaults.plan_reviewer` in `.ai/.ogre/config.json`, then `claude`. **Never add `--reviewer`/`--model` on your own initiative "to be explicit" or "to be safe" when the user's own message didn't name one - omit both and let `config.json` resolve it.** A real caught bug: a driving session hardcoded a specific rescuer/model on a project whose config had a different provider set as default, silently overriding it with no user request behind it. If you don't know the project's configured default, check `ogre config` first or simply omit the flag - don't guess. - `--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 t