What problem does it solve? Work handed off from a Kanban implementation lane needs independent verification before completion, and rubber-stamping handoff summaries lets defects slip through. This Skill gives a reviewer agent a structured procedure to verify deliverables against acceptance criteria and record an evidence-backed verdict. ## Core Features & Use Cases - Independent verdict routing: Approve via kanban_complete, request changes via kanban_request_changes, or escalate via kanban_block, each with concrete recorded evidence. - Round-based review lenses: Rotate between artifact, execution, and contract lenses across review rounds so each re-review catches different defect classes instead of repeating the same inspection. - Role separation enforcement: The reviewer never edits the implementation; corrections go back to the original implementer, and reviewer provenance routes re-reviews to the same reviewer. - Use Case: An implementer marks a bug-fix task review_requested. The reviewer reads the task with kanban_show, checks out the diff, runs the project's tests, finds one acceptance criterion unmet, and files actionable findings before returning the task for rework. ## Quick Start Review the current Kanban task in the review lane by reading its handoff with kanban_show, verifying the deliverable against the acceptance criteria, and submitting an approve, request-changes, or escalate verdict with evidence.