/resolve-dispute
Resolves stuck review findings via a put-up-or-concede exchange. Invoked by the facilitator when a finding survives arbitration without new evidence.
$ npx -y skills add DheerG/swarms --skill resolve-dispute --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/resolve-dispute
Context preview
The summary Claude sees to decide when to auto-load this skill.
Resolves stuck review findings via a put-up-or-concede exchange. Invoked by the facilitator when a finding survives arbitration without new evidence.
SKILL.md
resolve-dispute.SKILL.mdname: resolve-dispute
user-invocable: false
description: |
Resolves stuck review findings via a put-up-or-concede exchange. Invoked by the facilitator when a finding survives arbitration without new evidence.
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 more
name: resolve-dispute user-invocable: false description: | Resolves stuck review findings via a put-up-or-concede exchange. Invoked by the facilitator when a finding survives arbitration without new evidence.
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
Describe what you want. Get a reviewed, ship-ready PR — without babysitting the agent.
Other skills on swarm.
- /audit-context
Evaluates ambient context artifacts (CLAUDE.md, memory, local skills, settings hooks) for compatibility with swarm governance. Returns a classified report so users can address interference before launching a team.
Open skill - /code-mode
Code mode operational spec for the team lead. Returns lead identity, facilitator identity, mode-specific rules, suggest-members guidance, and phase arc for code-mode teams.
Open skill - /define-rubric
Builds measurable validation criteria when no existing standards apply. Invoked by team agents during review.
Open skill - /gate-presentation
Returns the frozen gate constants — question, header, option labels and descriptions, digest field-list, and preview content — for every catalog gate. Invoked by the team lead fresh on arrival at each gate and on pulse re-emissions, in the same turn as the render. The transport
Open skill - /general-mode
General mode operational spec for the team lead. Returns lead identity, facilitator identity, suggest-members guidance, and phase arc for general-purpose teams. The silent fallback when outcomes fit no specific mode, and a wrapper base for custom workflows — it has no shortcut
Open skill - /independent-review-loop
Independent review loop run before delivery in code work. An independent reviewer (Codex, or fresh Codex-style subagents) reads the whole PR against the approved outcome; the lead fixes in-scope functional findings and re-reviews until none remain. Its differentiator is
Open skill

