sadd-judge-with-debate

Evaluate solutions through multi-round debates among independent judges.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/vaur94/opencode-multiagent --skill sadd-judge-with-debate-vaur94
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sadd-judge-with-debate
Source: https://github.com/vaur94/opencode-multiagent/tree/main/skills/sadd-judge-with-debate
Command: npx skills add https://github.com/vaur94/opencode-multiagent --skill sadd-judge-with-debate-vaur94

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates a rigorous, multi-agent evaluation process to achieve consensus on solutions, overcoming the limitations of single-judge assessments and preventing groupthink.

Core Features & Use Cases

  • Iterative Debate: Judges challenge each other's assessments in multiple rounds, refining evaluations.
  • Consensus Building: Aims for agreement on scores and qualitative feedback, ensuring robust decision-making.
  • Use Case: Evaluating code submissions where multiple perspectives are needed to identify subtle bugs, design flaws, or areas for improvement, leading to a more objective and well-rounded assessment.

Quick Start

Use the sadd-judge-with-debate skill to evaluate the solution at 'src/api/users.ts' based on correctness, design, security, performance, and documentation criteria.

Frequently Asked Questions about sadd-judge-with-debate

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

FAQPage Schema
How does multi-agent debate improve code review quality compared to a single judge?

Multi-agent debate improves code review by using independent judges who challenge each other's assessments across multiple rounds. This iterative argumentation prevents groupthink and refines evaluations, overcoming the limitations and biases of single-judge assessments.

What is the best way to evaluate code submissions for design flaws and security issues objectively?

The best way to evaluate code submissions objectively is to use a multi-judge debate process. It facilitates structured argumentation and evidence-based challenges across criteria like correctness, security, and performance until a consensus is reached.

How do I reach consensus on design proposals when multiple reviewers disagree?

You reach consensus on design proposals by applying a multi-round debate among independent judges. The process drives iterative refinement of evaluations through structured argumentation until all judges agree or the maximum debate rounds are exhausted.

Can I use multi-round debate for evaluating solutions beyond just code?

Yes, you can use multi-round debate for evaluating any solutions requiring high-quality, objective assessments. The consensus-building mechanism applies effectively to designs, proposals, and other technical evaluations, not just code.

What happens if independent judges cannot reach an agreement during the evaluation?

If independent judges cannot reach an agreement during the evaluation, the multi-round debate process terminates safely. It exhausts the maximum configured debate rounds, ensuring the evaluation concludes without hanging.

Does multi-judge consensus building require external dependencies or specific environments?

Multi-judge consensus building requires no external dependencies to function. It operates standalone using provided scripts and references, allowing you to implement the evaluation process directly within your existing software engineering environment.