/review-plan

name: review-plan
description: "Review a plan by running internal reviews and a peer review in parallel and returning combined findings. Use when the user asks to \"review my plan\", \"check my plan\", \"critique my plan\", or wants feedback on a plan."

Review Plan

Review a plan against structure and scope criteria. Runs internal reviews and `/peer-review` in parallel by default. Returns combined structured findings.

Step 1: Resolve the Plan

1. **Plan text in conversation** — use it 2. **Explicit path** — read it 3. **Explicit slug** — resolve to `.turbo/plans/<slug>.md` 4. **Single file** — Glob `.turbo/plans/*.md`. If exactly one file exists, use it 5. **Most recent** — most recently modified file 6. **Legacy fallback** — `.turbo/plan.md` if `.turbo/plans/` does not exist 7. **Nothing found** — stop and state that no plan was found to review

When the plan came from a file, state the resolved path before continuing.

Unless the plan came from conversation text, or an explicit path or slug was passed, check whether the resolved plan still describes work that remains to be done. Report a frontmatter `status:` of `done` alongside the path.

Step 2: Run Reviews in Parallel

Two reference files carry the criteria, one per internal review:

• [references/plan-structure-review.md](references/plan-structure-review.md)
• [references/plan-scope-review.md](references/plan-scope-review.md)

Skip peer review when instructed (e.g., "without peer review", "no peer", "internal only").

When a list of already-adjudicated findings was supplied (one line each: the finding, its verdict, and the recorded reason), include it in every agent's prompt, internal and peer, labeled as decisions already reached on proposed revisions rather than as established properties of the plan. Direct each agent to treat a finding as listed when it matches one on both location and substance, to raise such a finding again only on evidence its recorded reason does not already account for, and to judge any other finding at the same location on its own merits.

Emit all Agent tool calls below in one assistant message. Each Agent call uses `model: "opus"` and no `name`. Wait for every agent to report before continuing. Do not begin the next step on a partial set, and do not relaunch an agent that has not yet reported. That is three Agent tool calls when peer review is active (two internal + one peer), or two Agent tool calls when peer review is skipped. Every agent's prompt must direct it to treat the shared working tree and its git index as read-only and to assess findings by reading and reasoning. HEAD stays where it is: read other refs with `git show <ref>:<path>` rather than `git checkout` or `git switch`. For a check that requires mutating code, the agent works in an isolated `git worktree` created under `$TMPDIR` and discarded afterward. Refer to that worktree by absolute path in every command and join chained steps with `&&`, so a failed step cannot leave the rest running in the shared checkout. Run teardown and verification as their own commands. Give that worktree its own dependency install rather than reaching the shared tree's install by any route: removing a worktree deletes through symlinks, and a redirected suite writes into the shared install. When its own install is not possible, the check is left unrun and reported as such. A check that runs in the shared checkout invokes an already-installed runner directly wherever a package-manager wrapper would front it, since such a wrapper reads as read-only while reconciling the shared install before it runs. Confine dependency installs and reconciliation to an isolated worktree. Afterward the agent verifies that `git worktree list` no longer shows the worktree, that `git status --short` is clean, and that HEAD is still on the branch it started on. After any check, in a worktree or in the shared checkout, it verifies that the shared tree's dependency directory still resolves (a destroyed install leaves `git status` clean, since it is gitignored). Damage the agent cannot repair is reported with the exact repair command in place of findings.

• **Structure Agent:** The subagent's prompt must include the plan text, the path to the structure reference file (`~/.claude/skills/review-plan/references/plan-structure-review.md`), the output format below, and this directive: read that reference file directly, apply its determination criteria as the bar for a real finding, then report every finding that clears that bar tagged with its priority and with `internal (structure)`. Coverage is the goal at this stage, so surface everything that qualifies and let the priority tags convey severity. The subagent must also return the Overall Verdict block for its dimension.
• **Scope Agent:** Same, with the scope reference file (`~/.claude/skills/review-plan/references/plan-scope-review.md`) and findings tagged `internal (scope)`.
• **Peer review Agent (unless skipping):** Launch an Agent tool call whose prompt instructs the subagent to invoke `/peer-review` via the Skill tool with a request describing: (a) the plan under review; (b) the criteria live in `~/.claude/skills/review-plan/references/plan-structure-review.md` and `~/.claude/skills/review-plan/references/plan-scope-review.md` — the reviewer should read both files directly and cover every criterion in one single-pass review, applying each file's determination criteria and priority scale to the findings in that file's domain; (c) the Overall Verdict should use the `Readiness: <ready | needs revision>` label; (d) the already-adjudicated findings list when one was supplied, framed as described above. The prompt must also state explicitly that the subagent's final assistant message must contain the verbatim findings text `/peer-review` produced.

Aggregate findings with attribution (reviewer: "internal" or "peer", each with its "structure" or "scope" dimension). Present them in the output format below.

Then use the Task