Verified:GitHub

judgment-day

Run two blind judge sub-agents in parallel to review code or architecture.

1|1|Updated Apr 19, 2026

Search Tags:#code-review #escalation #adversarial-review #parallel-review #iterative-fix #verdict-synthesis #judgment-day

Ready to run

npx skills add https://github.com/RamonsDka/the-architect-overlay --skill judgment-day-ramonsdka

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: judgment-day
Source: https://github.com/RamonsDka/the-architect-overlay/tree/main/skills/judgment-day
Command: npx skills add https://github.com/RamonsDka/the-architect-overlay --skill judgment-day-ramonsdka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Parallel adversarial review protocol that launches two independent blind judge sub-agents simultaneously to review the same target, synthesizes their findings, applies fixes, and re-judges until both pass or escalates after 2 iterations.

Core Features & Use Cases

Parallel blind review by two independent judges, producing diverse findings with no cross-contamination.
Verdict synthesis that combines results into a structured outcome and triggers iterative fix-and-judge cycles or escalation.
Pre-merge and high-stakes audits where independent perspectives reduce risk and improve confidence in changes.

Quick Start

Say "judgment day" to start a parallel blind review of a chosen target.

Frequently Asked Questions about judgment-day

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run parallel adversarial code reviews for pre-merge verification?▼

Parallel adversarial code reviews launch two independent blind judges simultaneously to examine the same target, preventing cross-contamination. The process synthesizes their findings into a structured verdict to resolve high-stakes pre-merge checks.

Can I use independent judge reviews for critical architecture audits?▼

Yes, independent judge reviews are best suited for critical architecture audits and high-stakes feature reviews. The dual-judge protocol ensures diverse perspectives examine your development artifacts, reducing risk and improving confidence in changes.

What happens when iterative code fixes fail to pass the review cycle?▼

When iterative code fixes fail to resolve issues after two re-judge cycles, the protocol triggers an escalation pathway. This structured verdict synthesis ensures persistent problems during high-stakes reviews are formally escalated rather than ignored.

How does the dual-judge protocol synthesize findings from blind reviews?▼

The dual-judge protocol synthesizes findings by combining results from two blind, parallel reviews into a structured outcome. If issues remain, it applies fixes and initiates iterative fix-and-rejudge cycles until both judges pass.

Do I need to provide specific development artifacts for parallel code reviews?▼

Yes, you must provide the specific development artifacts or code targets intended for review. The parallel blind review process requires a defined target to initiate the dual-judge protocol and generate a synthesized verdict.