judgment-day

When to Use

• User explicitly asks for "judgment day", "judgment-day", or equivalent trigger phrases
• After significant implementations before merging
• When high-confidence review of code, features, or architecture is needed
• When a single reviewer might miss edge cases or have blind spots
• When the cost of a production bug is higher than the cost of two review rounds

Critical Patterns

Pattern 0: Skill Resolution (BEFORE launching judges)

Follow the Skill Resolver Protocol (_shared/skill-resolver.md) before launching ANY sub-agent:

1. Obtain the skill registry (engram → .atl/skill-registry.md from the project root → skip if none)
2. Identify the target files/scope — what code will the judges review?
3. Match relevant skills from the registry's Compact Rules by:
   • Code context: file extensions/paths of the target (e.g., .tsx → react-19, typescript)
   • Task context: "review code" → framework/language skills; "create PR" → branch-pr skill