sadd:judge-with-debate

Coordinate three judge agents in iterative debates to produce consensus evaluations.

2|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/fockus/claude-skill-build --skill sadd-judge-with-debate-fockus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sadd:judge-with-debate
Source: https://github.com/fockus/claude-skill-build/tree/main/skills/sadd-judge-with-debate
Command: npx skills add https://github.com/fockus/claude-skill-build --skill sadd-judge-with-debate-fockus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates rigorous solution evaluation by coordinating independent judges in multi-round debates to reach consensus, improving fairness, transparency, and quality assurance.

Core Features & Use Cases

  • Meta-Judge generates tailored evaluation specifications used by three independent judges across all rounds.
  • Phase 1 Independent Analysis: three judges produce initial assessments with evidence per criterion.
  • Phase 2 Debate Rounds: iterative exchanges where judges defend, challenge, and revise scores (up to 3 rounds) until consensus or human review.
  • Phase 3 Consensus evaluation: check for overall score convergence, export a final consensus report.

Quick Start

Create and run an evaluation workflow for a given solution path to obtain a consensus report.

Frequently Asked Questions about sadd:judge-with-debate

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

FAQPage Schema
How do I automate multi-agent consensus evaluation for code and documentation?

Multi-agent consensus evaluation is automated by coordinating independent judges in iterative debate rounds. Three separate judge agents analyze solutions against a shared evaluation specification, defending and revising scores up to three rounds until reaching overall score convergence.

What is a multi-round debate approach for automated solution evaluation?

A multi-round debate approach for evaluation uses independent judges to produce initial assessments with evidence per criterion. Judges then engage in iterative exchanges to defend, challenge, and revise scores over up to three rounds until a consensus report is generated.

How do I set up a multi-judge evaluation workflow with independent agents?

To set up a multi-judge evaluation workflow, a meta-judge first generates a tailored evaluation YAML specification. Three separate judge agents then use this shared specification to perform independent analysis, exchanging filesystem-based reports to debate and reach consensus.

Can I use rubrics and a meta-judge to standardize automated evaluation across different solutions?

Yes, rubrics and a meta-judge standardize automated evaluation by generating a shared evaluation specification YAML. This tailored rubric is applied across all three independent judges and iterative debate rounds to ensure fair, evidence-driven consensus for any code or documentation solution.

What happens if independent judges cannot reach score convergence during the debate rounds?

If independent judges cannot reach score convergence during the debate rounds, the process supports escalation to human review. The multi-round debate runs up to three rounds of iterative exchanges where judges defend and challenge scores before this fallback is triggered.

Does automated multi-judge consensus require any external dependencies or components?

No, automated multi-judge consensus requires no external dependencies or components. The workflow operates entirely through a meta-judge generating evaluation specifications, three independent judge agents, and filesystem-based report exchanges to coordinate the iterative debate rounds.