judge

Evaluate convergence across agent refinements and generate final synthesis documents.

3|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/slior/dialectic-agentic --skill judge-slior
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: judge
Source: https://github.com/slior/dialectic-agentic/tree/main/.cursor/skills/judge
Command: npx skills add https://github.com/slior/dialectic-agentic --skill judge-slior

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluates convergence across agent refinements and, when the debate ends, writes the final synthesized solution.

Core Features & Use Cases

  • Convergence evaluation across per-round refinements according to configurable criteria.
  • Synthesis generation to produce a comprehensive final solution document after convergence.
  • Workspace-aware processing: reads refinements, verdicts, and configuration from the debate workspace to ensure traceability.

Quick Start

Instruct the judge to run convergence checks or synthesis against the active debate workspace.

Frequently Asked Questions about judge

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

FAQPage Schema
How do I evaluate convergence across multi-agent debate refinements?

To evaluate convergence across multi-agent debate refinements, use the convergence_check mode to generate per-round verdicts. It reads agent refinements and configuration from the workspace, outputting results to debate/round-N/verdict.json for each round.

How does final synthesis generation work after a multi-agent debate ends?

Final synthesis generation works by reading all refinements and verdicts from the debate workspace to produce a comprehensive solution document. It outputs the final synthesized solution to debate/synthesis.md, including any open issues when needed.

What's the best way to track per-round verdicts in a multi-agent debate?

The best way to track per-round verdicts is using the convergence_check mode, which evaluates agent refinements against configurable criteria. It writes structured per-round verdict files to the debate/round-N/verdict.json path within your workspace.

Do I need to configure criteria before checking convergence in a multi-agent debate?

Yes, you need to define convergence criteria in your configuration before checking convergence. The judge reads this configuration from the active debate workspace to evaluate agent refinements and determine if convergence has been reached.

Can I generate a final synthesis document with open issues from a multi-agent debate?

Yes, you can generate a final synthesis document that explicitly includes open issues. When the debate ends, the synthesis mode reads workspace refinements and writes the final solution to debate/synthesis.md, noting unresolved items when needed.

Why does convergence evaluation require workspace-aware processing for multi-agent debates?

Convergence evaluation requires workspace-aware processing to ensure traceability across rounds. By reading refinements, verdicts, and configuration directly from the debate workspace, the judge maintains a consistent context for accurate per-round and final synthesis.