judgment-day

## 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. Within this QA boilerplate, this skill is cited as an OPTIONAL adversarial augmentation by: - `/test-automation` — Review phase for high-risk test changes - `/git-flow-master` — pre-PR gate when the diff is large or touches shared fixtures / base classes - `/framework-development` — pre-archive review of framework evolution diffs It is never invoked automatically. Users opt in via explicit trigger. ## Inputs — read these first, in this order Canonical reading order for any AI starting cold on a Judgment Day review. Read in order; stop earlier when the target is small enough that later inputs add no signal. 1. The diff / files / PR / architecture slice under review — the literal target the user named. 2. `CLAUDE.md` — repo conventions, Critical Rules, behavioral layer (the judges must score against these, not generic best-practice). 3. `.claude/skills/REGISTRY.md` — skill registry; resolve which project skills apply to the target's file paths + task type, and inject the same `Skills to load before work` block into both judge prompts. 4. The change's spec / PR description / Jira ticket — the stated intent. Judges score against intent, not their imagined intent. 5. `references/prompts-and-formats.md` — judge prompts, fix prompts, w...