What problem does it solve? Deterministic checks like string comparisons and lint rules cannot judge whether an analysis interprets scope correctly, whether a plan is sound, or whether an implementation faithfully matches what the user asked for. This Skill adds a model-based quality gate on top of ORC's deterministic gates to catch those judgment-level failures. ## Core Features & Use Cases - Three dispatch contexts: gate=analysis (after the analyst), gate=plan (after the planner), and gate=implementation (after verify), each judging a different artifact against fixed ground truth. - Structured verdicts: returns APPROVE, REVISE, or ESCALATE with anchored, consequence-cited findings; REVISE loops the author with a hard 2-loop cap and a convergence rule. - Anti-anchoring design: the judge is read-only, blind to the author's self-assessment, and never fixes anything itself — authors fix. - Use Case: During an /orc-ultra run, after the planner finishes, the orchestrator dispatches the judge at gate=plan to validate decomposition, declared-file plausibility, and blast-radius coverage before any code is written. ## Quick Start Run /orc-ultra on a feature request and the orchestrator will automatically dispatch the judge agent at each of the three ultra gates.