| name | plan-review |
| description | Use when a plan should be challenged, approved, or refined before implementation starts, with agmo-critic/agmo-architect/verifier routing as needed. |
| argument-hint | [current plan, plan note, or review request] |
Agmo Plan Review
Use this when the current plan should be challenged, validated, or refined before execution.
Main-session contract
The main session must not self-approve its own plan.
When $plan-review is invoked, the main session should:
- keep the active workflow in the planning lane
- gather missing repo facts with
agmo-explore before judging plan assumptions tied to current files or symbols
- hand the review pass to the right lane instead of improvising approval in place
- default challenge lane:
agmo-critic
- boundary and tradeoff review:
agmo-architect
- acceptance criteria / verification review:
agmo-verifier
- revision support when needed:
agmo-planner
- return a clear verdict: approve, revise, or reject/re-plan
Native subagent lifecycle
When spawning native subagents for this workflow, keep each agent id until its result is integrated, then call close_agent for completed, failed, superseded, or no-longer-needed lanes so thread slots are released before the next delegation.
Review targets
Check the plan for:
- vague or untestable acceptance criteria
- missing file ownership or execution boundaries
- hidden dependency order
- assumptions that need repo evidence
- unresolved non-goals or decision boundaries
- weak verification shape
- task chunks that are still too large
Important behavior
- keep this as a plan-stage review, not a generic execution verification pass
- combine reviewer lanes only when they answer different questions
- keep durable context anchored to the plan lane so execution can continue from the same artifact
Handoff
- if approved, the next likely step is
execute
- if revisions are needed, return to
plan
- if the review exposes deeper uncertainty, go back to
brainstorming
Artifact save body
Before ending a meaningful plan-review stage, make the final response or delegated result save-ready:
- reviewed plan target
- verdict and rationale
- required revisions or approval notes
- verification concerns
- next workflow handoff
