disagreement-resolution

Adjudicate competing AI approaches with discriminating tests and preserved dissent.

Updated Dec 12, 2025
One-click install
npx skills add https://github.com/eaasxt/Farmhand --skill disagreement-resolution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: disagreement-resolution
Source: https://github.com/eaasxt/Farmhand/tree/main/config/skills/disagreement-resolution
Command: npx skills add https://github.com/eaasxt/Farmhand --skill disagreement-resolution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating decisions between competing AI agents or approaches is complex and prone to bias or indecision. This skill provides a structured, test-based adjudication workflow that yields transparent, evidence-backed choices and preserves valid dissent.

Core Features & Use Cases

  • Orchestrated decision workflows using an orchestrator-subagent pattern, with isolated context per phase to avoid anchoring.
  • Generation of discriminating tests, execution of tests, and formal adjudication culminating in a clear winner or preserved dissent with user input when needed.
  • Supports architectural tradeoffs and multi-agent collaboration in domains like AI research, software design, and complex automation.

Quick Start

Start a four-phase disagreement-resolution workflow to compare two AI approaches and produce a documented, test-backed decision.

Frequently Asked Questions about disagreement-resolution

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

FAQPage Schema
How do I resolve disagreements between competing AI agents in a multi-agent architecture?

Multi-agent disagreement resolution works through an orchestrator-subagent pattern that isolates context per phase to avoid anchoring, generates discriminating tests, executes them, and formally adjudicates a clear winner or preserved dissent.

What is test-based adjudication for AI architectural tradeoffs?

Test-based adjudication for architectural tradeoffs is a structured workflow where competing AI approaches are evaluated by generating and executing discriminating tests, yielding transparent, evidence-backed choices instead of biased or indecisive outcomes.

When should I use an orchestrator pattern for multi-agent decision-making?

Use an orchestrator pattern for multi-agent decision-making when multiple valid approaches exist, users ask which approach to take, or architectural tradeoffs must be decided with structured, test-backed evaluation and preserved dissent.

How do I start a four-phase disagreement-resolution workflow to compare two AI approaches?

Start a four-phase disagreement-resolution workflow by initiating the orchestrator-subagent pattern, which isolates context per phase, generates discriminating tests, executes them, and produces a documented, test-backed decision.

Does multi-agent disagreement resolution work without external dependencies?

Multi-agent disagreement resolution works without external dependencies, using an internal orchestrator-subagent pattern with isolated context per phase to generate tests and adjudicate competing AI approaches independently.

What are the limitations of test-based adjudication for complex AI automation decisions?

A limitation of test-based adjudication is that when discriminating tests fail to produce a clear winner, the workflow must preserve dissent and request user input, potentially halting automated decision-making in complex architectural tradeoffs.