debate

Orchestrate structured adversarial debates between AI agents with blinded scoring.

4|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/EZotoff/ez-omo-config --skill debate-ezotoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debate
Source: https://github.com/EZotoff/ez-omo-config/tree/main/skills/debate
Command: npx skills add https://github.com/EZotoff/ez-omo-config --skill debate-ezotoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a reproducible, bias-resistant protocol for running structured adversarial debates between AI agents so teams can surface hidden assumptions, stress-test arguments, and reach evidence-based decisions without human bias in scoring.

Core Features & Use Cases

  • Blinded multi-agent orchestration: Labels participants as Alpha/Beta and enforces deterministic assignment rules to prevent judge bias.
  • Segmented debate flow & scoring: Enforces S1–S4 segment structure, per-segment 1–10 scoring with one-sentence justifications, and mechanical recomputation of totals.
  • Persist-on-collect reliability: Immediately writes raw judge background outputs to disk before parsing, with malformed-output handling and retry/recovery policies.
  • Multiple modes: Supports quick 1:1 challenges, full formal debates with rounds and judges, panel reviews, pre-mortems, red teams, and architecture adversary workflows.
  • Use Case: Use this Skill to run a three-round, 3-judge blind debate on an architectural decision, collect judge verdicts, and produce an auditable transcript and final verdict.

Quick Start

Start a formal three-round blinded debate with three judges and persist all judge outputs to .sisyphus/debates/{topic}.

Frequently Asked Questions about debate

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

FAQPage Schema
How do I run a blinded multi-agent debate to evaluate competing architecture decisions?

To run a blinded multi-agent debate, this Skill orchestrates participants under Alpha/Beta labels with deterministic assignment rules, enforcing a segmented S1–S4 structure with per-segment 1–10 scoring to prevent judge bias and reach evidence-based technical decisions.

What is the best way to automate red team analysis and pre-mortems across AI agents?

The best way to automate red team analysis and pre-mortems is using structured adversarial orchestration, which applies sequential round workflows and blinded judging to stress-test arguments and surface hidden assumptions without human scoring bias.

How does adversarial analysis handle judge failures or malformed outputs during panel reviews?

Adversarial analysis handles judge failures through a persist-on-collect reliability mechanism that immediately writes raw judge outputs to disk before parsing, applying malformed-output handling alongside retry and quorum recovery policies to ensure auditable transcripts.

Can I use multi-agent orchestration for quick one-to-one technical challenges without a full panel?

Yes, multi-agent orchestration supports multiple modes including quick 1:1 challenges, allowing you to evaluate technical positions without the overhead of full formal debates, sequential rounds, or a multi-judge quorum.

When should I not use blinded debate orchestration for decision-making?

You should avoid blinded debate orchestration when decisions require subjective human intuition rather than evidence-based technical evaluation, as the Skill enforces mechanical recomputation of scoring totals and rigid segment structures.

Does multi-agent debate orchestration persist judge verdicts and transcripts to disk automatically?

Yes, multi-agent debate orchestration automatically persists raw judge background outputs to disk upon collection, storing them in a designated directory path to produce auditable transcripts and final verdicts for architecture reviews.