review-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 and read it
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-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.

Pass the plan to every agent, internal and peer, the same way: for a plan that is on disk, name its absolute path and direct the agent to read the file in full; for a plan that exists only as conversation text, include that text.