agentleFS
yogsoth-aiyogsoth-ai/convergence/skills/adversarial-debate-protocol/SKILL.md

adversarial-debate-protocol

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

Structured debate protocol that constructs an advocate, deploys critic attacks, and renders a judge verdict through iterative rounds.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If judge verdict is REVISE, advocate must address specific weaknesses identified

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Adversarial Debate Protocol

A formal three-role debate structure ensuring decisions survive rigorous adversarial challenge. The protocol assigns distinct roles (advocate, critic, judge) to prevent confirmation bias and ensure intellectual honesty.

Stages

  1. Advocate Construction — Build the strongest possible case for the position under debate
  2. Critic Attack — Attack the advocate's case from multiple angles with severity ratings
  3. Judge Verdict — Impartial assessment of advocate case vs critic attacks, rendering ACCEPT/REJECT/REVISE
  4. Iteration (if REVISE) — Advocate revises case, critic re-attacks, judge re-evaluates

Available SOPs

SOPRolePurpose
advocate-constructionAdvocateBuild strongest case for position
critic-attackCriticAttack the case with rated arguments
judge-verdictJudgeRender impartial verdict

Execution Guidance

  • Minimum 2 rounds before accepting ACCEPT verdict
  • Critic must produce >= 3 distinct attack arguments per round
  • Judge must address every critic argument explicitly
  • If judge verdict is REVISE, advocate must address specific weaknesses identified
  • Maximum 4 rounds before escalating to strategy level

Minimum Yield

  • Advocate case with explicit evidence and reasoning
  • Critic attacks with severity ratings (HIGH/MEDIUM/LOW)
  • Judge verdict (ACCEPT/REJECT/REVISE) with point-by-point reasoning
  • Conditions for acceptance (if ACCEPT)
  • Required modifications (if REVISE)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.