What problem does it solve? It gives a reviewer agent a consistent, evidence-based procedure for judging code changes against the contract they were meant to satisfy, replacing ad-hoc review with a structured verdict and findings workflow. ## Core Features & Use Cases - Three review scopes: Route to task, phase, or final review based on spawn context, each with its own contract (task handoff, phase plan, or requirements doc) and diff range. - Two-lens judgment: Evaluate every diff for conformance against its contract and for engineering quality, merging both into one numbered findings list with severity levels. - Running review reports: Maintain a single report per scope across corrective cycles, adjudicating coder fixes and disputes in place rather than re-reviewing from scratch. - Use Case: A reviewer agent receives a task commit SHA and handoff document, runs the diff and tests itself, and writes a review report with an approved, changes_requested, or rejected verdict backed by file:line evidence. ## Quick Start Review the diff for the task identified in my spawn context against its handoff and write the review report with a verdict.
