full-review
Full Review
Choose the branch before selecting a model. Coordinator-only review and deterministic evidence work proceed within invocation authority. Apply routine review lenses in the assigned reviewer context. For a worker dispatch, use shared/references/model-preview.md and its one approved route snapshot. Nested skills, runners, and rechecks consume that snapshot. They do not select another route or worker.
For a worker dispatch, model IDs, effort support, and task defaults come only
from shared/model-routing.json. Preserve the exact saved route during
dispatch, retry, and resume.
Review the risks that a focused implementation pass cannot see. The result is a precise, evidence-backed verdict. The next consumer is the author or delivery workflow. A review is complete when its scope, evidence, findings, verification limits, and verdict are explicit.
Review plan
The review plan is a scope contract. Do not claim coverage outside it. It states scope, risk, seats, effort, and verification. In a delivery workflow, derive it from the user-approved routing-plan JSON. That JSON is the exact executable source for seat, runner, model, effort, mode, and unavailable action.
| Scope | Use when | Minimum review shape |
|---|---|---|
focused |
One bounded change with local risk | One review seat and relevant deterministic checks. |
seam |
Integrated tasks, shared contracts, or cross-boundary behavior | Approved route or routes that cover logic and state plus root-cause precision. Add a second route only when the plan names it. |
deep |
Explicit deep request, security-sensitive boundary, migration, public contract, or high residual risk | The seam shape plus selected security, data, compatibility, or structural specialists. |