What problem does it solve? It prevents teams from treating "code written" or "tests compiled" as done by requiring a structured review of the actual diff, current verification evidence, and accepted behavior before a workstream is closed. ## Core Features & Use Cases - Evidence-Based Acceptance: Compares the integrated result against the workstream's accepted outcome, regression risk, security, data integrity, and architecture ownership, then records PASS, FIX_REQUIRED, or BLOCKED. - Independent Review Delegation: For non-trivial workstreams, it dispatches a read-only subagent review so completion is not decided solely by the implementation context. - Blocking vs Non-Blocking Findings: Each finding gets a concrete location, evidence, impact, and smallest useful repair direction, separating blockers from optional improvements. - Use Case: Before closing a full-stack feature, run a review that requires current contract or integration evidence plus an end-to-end user path, catching a stale test result that no longer matches the reviewed implementation. ## Quick Start Ask the assistant to review the current change against the accepted outcome and verification evidence before closing the workstream.
