What If AI Agents Debated Each Other? Redesigning the Development Process Through Multi-Agent Collaboration (opens in new tab)

AI coding’s main bottleneck is no longer code generation but the human coordination surrounding it: clarifying intent, validating assumptions, testing implementations, and preparing trustworthy pull requests. LY Corporation proposes an AI-native pipeline in which specialized “proposer” and “challenger” agents debate across three stages—specification, build, and delivery—while an orchestrator decides whether to revise, escalate, or proceed. The goal is for AI to substantiate its own work before human engineers review and approve it.

Human Coordination as the Bottleneck

• Traditional AI-assisted development speeds up individual tasks but leaves handoffs between requirements, implementation, verification, and review to humans.
• Engineers still need to:
  • Write or refine specifications
  • Review AI-generated drafts
  • Transfer failed tests and feedback between steps
  • Inspect diffs
  • Prepare PR descriptions
  • Decide whether the result is trustworthy
• The proposed solution is not to remove human judgment, but to automate repetitive coordination while preserving human ownership and final approval.

Proposer–Challenger Collaboration

• AI responsibilities are divided between two opposing groups:
  • Proposers develop specifications, implementations, and delivery materials.
  • Challengers validate them from specialized perspectives.
• The separation prevents one general-purpose assistant from combining design, implementation, testing, and review into a single unchallenged response.
• Specialized roles may include:
  • requirements-synthesizer
  • security-analyst
  • test-coverage-reviewer
  • technical-writer
  • evidence-verifier
• An orchestrator mediates disagreements, redirects discussions, resolves deadlocks, and determines whether to revise, escalate, or advance.

The Spec–Build–Deliver Pipeline

Specification

• The specification acts as a contract for all later stages.
• It records:
  • Goals and constraints
  • Interpreted requirements
  • Explicit assumptions
  • Open questions
  • Proposed approach
  • Definition of done
• Agents use evidence from the workspace and external sources such as Jira, Confluence, design documents, APIs, tests, dependencies, and existing conventions.
• Ambiguous but low-risk and reversible issues can be documented as assumptions.
• Unsafe, destructive, externally constrained, or hard-to-reverse uncertainties are escalated instead of guessed.

Build

• The approved specification is converted into a test-first verification plan before production code is changed.
• The proposer identifies expected behavior, edge cases, required tests, and execution commands.
• Challengers can dispute the verification design before or during implementation.
• Proposers must support rejected objections with concrete evidence such as:
  • Execution paths
  • Compiler or linter output
  • Failing tests
  • Other workspace evidence
• This prevents a simple green CI result from hiding missing or inadequate validation.

Delivery

• The final output is a review-ready PR package rather than merely a diff summary.
• It explains:
  • What changed
  • Where reviewers should look first
  • Which checks passed
  • Remaining risks
  • Which challenges were already investigated
• At this stage, the orchestrator acts more like a jury, judging whether sufficient evidence exists for release.

Structured Debate Protocol

• Each agent receives stage-specific context and returns structured JSON rather than a free-form essay.
• Agents do not share one live context window. Shared state consists of:
  • Workspace files
  • Generated artifacts
  • The orchestrator’s accumulated transcript
• Each round includes a proposer response, challenger response, and orchestrator decision.
• The protocol distinguishes manageable uncertainty from blocking risk.
• Consistent schemas make agent outputs easy to parse, compare, and feed into subsequent rounds.
• For example, a challenger can identify an unclear scope boundary, explain why it matters, assign severity and confidence, and indicate whether user input is required.

Overall Impact

• Issues move through a continuous chain: debated specification, branch, tested implementation, and review-ready PR.
• Humans intervene mainly to define intent, approve the final result, or resolve explicitly escalated decisions.
• The central leverage comes not from generating code faster, but from requiring AI to explore, challenge, verify, and package its work before asking engineers to pay attention.

The practical recommendation is to redesign AI development around explicit artifacts, specialized adversarial roles, evidence-based decisions, and automated handoffs. Human engineers should remain the final decision-makers, while AI handles the intermediate coordination and proof-building work.