resolve-dispute
This skill structures the resolution of stuck review findings through a three-step process: framing the dispute by identifying the contested finding and prior ruling, requesting specific evidence from the reviewer in one of three forms (failure scenario, source citation, or counterexample), and then issuing a final ruling that tags the finding as DECIDED. Use it after standard arbitration has stalled and a finding remains contested, ensuring disputes progress to closure while preserving the option to reopen with substantive new evidence.
git clone --depth 1 https://github.com/DheerG/swarms /tmp/resolve-dispute && cp -r /tmp/resolve-dispute/skills/resolve-dispute ~/.claude/skills/resolve-disputeSKILL.md
A review finding is stuck. Structure its resolution in three steps. **Step 1 — Frame the dispute.** Identify and state aloud: - The disputed finding (one sentence) - Who holds it - The facilitator's prior arbitration ruling (one sentence) **Step 2 — Send the reviewer this message, substituting `[finding]` with the actual finding:** > Your finding — [finding] — was arbitrated. To keep it open, you must provide ONE of: > (a) A concrete failure scenario: specific inputs or conditions that produce wrong behavior > (b) A source citation: file, line number, and what it shows > (c) A direct counterexample to the arbitration reasoning > > One response. No response counts as concession. After that, the facilitator rules and the finding is DECIDED. **Step 3 — Rule and tag.** After the reviewer responds: - Evidence present → the facilitator evaluates it on the merits and rules. Tag the finding DECIDED regardless of outcome. - No evidence → the facilitator tags DECIDED, asks the reviewer to re-score. - No response → the facilitator tags DECIDED. DECIDED findings cannot be re-raised without new substance. This enforces the existing "Don't regurgitate decided points" rule. **What this skill must not do:** - Override a finding backed by real evidence - Auto-resolve — the facilitator still decides after hearing the evidence - Apply to first-round disagreements — use normal arbitration first - Suppress legitimate concerns — evidence always reopens the door
Read-only swarm team member. Spawned by swarm via Agent tool with team_name. Tools restricted to read and research only — no Edit, Write, or NotebookEdit. Operational guidance comes from the briefing template at spawn time.
Launch a code-mode agent team
Scaffold a custom workflow — generates a mode skill and shortcut command
Launch a general-mode agent team
Interactively launch an agent team with guided setup
Walk through swarm's core concepts and launch your first team
Run recursive refinement on the current branch and PR
Launch a triage-mode agent team — diagnose an issue without changing it