dispute

Coordinate structured cross-model debates among Claude, GPT, and Gemini to reach consensus on architecture decisions.

25|10|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/neuron-one/GODMODE --skill dispute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dispute
Source: https://github.com/neuron-one/GODMODE/tree/main/skills/workflow/dispute
Command: npx skills add https://github.com/neuron-one/GODMODE --skill dispute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-model disputes coordinate independent positions from Claude, GPT, and Gemini, then iteratively negotiate to reach consensus on architecture and technical decisions.

Core Features & Use Cases

  • Independent positions from three models, evaluated in parallel
  • Round-based critiques and defenses, with structured consensus checks
  • Use cases: stack choices, architecture decisions, or any critical technical decision
  • Fallback to 2-model dispute if one model is unavailable

Quick Start

Initiate a cross-model dispute among Claude, GPT, and Gemini to decide on an architecture decision.

Frequently Asked Questions about dispute

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

FAQPage Schema
What is a cross-model dispute for architecture decisions?

A cross-model dispute coordinates independent positions from Claude, GPT, and Gemini to negotiate and reach consensus on critical technical decisions. It enforces independent initial positions, stepwise critiques, and bounded rounds to produce a final decision.

How do I get multiple AI models to reach consensus on a stack choice?

To reach consensus on a stack choice, initiate a cross-model dispute to generate independent positions from Claude, GPT, and Gemini. The workflow applies round-based critiques and defenses with structured consensus checks to finalize the architecture decision.

Can I still run a multi-agent debate if one AI model is unavailable?

Yes, you can still run a multi-agent debate if one model is unavailable. The cross-model dispute workflow includes a fallback mechanism that automatically transitions to a 2-model dispute to ensure the negotiation process continues.

When should I use cross-model negotiation for technical decisions?

Use cross-model negotiation for technical decisions requiring multiple perspectives, such as stack choices or architecture tasks. It is designed for critical decisions where independent initial positions and stepwise critiques help ensure a comprehensive evaluation.

How does the consensus check work in a multi-agent architecture debate?

The consensus check in a multi-agent architecture debate works through bounded rounds of round-based critiques and defenses. Models independently evaluate the task, iteratively negotiate their positions, and undergo structured consensus checks until a final agreement is reached.

Does cross-model dispute require any specific dependencies or components?

No, cross-model dispute requires no specific dependencies or components to function. It is an advanced workflow designed to coordinate debates among Claude, GPT, and Gemini without needing additional structural modules or external libraries.