judgment-daylisted

## Activation Contract Load this skill only when the user explicitly asks for Judgment Day, dual/adversarial review, or equivalent Spanish trigger (`juzgar`, `que lo juzguen`). Review a specific target: files, feature, PR, or architecture slice. ## Hard Rules - Resolve project skills before launching agents: read skill registry, match indexed paths by target files/task, and pass the same `Skills to load before work` block into both judge prompts and fix prompts. - Launch **two blind judges in parallel** with identical target and criteria; never review the code yourself. - Wait for both judges before synthesis; never accept a partial verdict. - Classify warnings as `WARNING (real)` only if normal intended use can trigger them; otherwise downgrade to INFO as `WARNING (theoretical)`. - Ask before fixing Round 1 confirmed issues. - After any fix agent runs, immediately re-launch both judges in parallel before commit/push/done/session summary. - Terminal states are only `JUDGMENT: APPROVED` or `JUDGMENT: ESCALATED`. - After 2 fix iterations with remaining issues, ask the user whether to continue. ## Decision Gates | Condition | Action | |---|---| | Target unclear | Ask for scope; do not launch judges. | | No skill registry | Warn, proceed with generic criteria, and record `Skill Resolution: none`. | | Both judges find same CRITICAL/real WARNING | Confirmed; ask/fix according to round rules. | | One judge finds issue | Suspect; report and triage, do not auto-fix. | | Judges co