跳到正文
cccskills
免费在 GitHub 公开

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.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md1.7 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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.

中文简介正在准备中。当前显示原文说明。

DheerG/swarms852026年7月23日 更新

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.

中文简介正在准备中。当前显示原文说明。

DheerG/swarms852026年7月23日 更新

Builds measurable validation criteria when no existing standards apply. Invoked by team agents during review.

中文简介正在准备中。当前显示原文说明。

DheerG/swarms852026年7月23日 更新

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 contract, three renders, partition rule, and authoring rubric live in swarm:workflow-rules.

中文简介正在准备中。当前显示原文说明。

DheerG/swarms852026年7月23日 更新

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 command.

中文简介正在准备中。当前显示原文说明。

DheerG/swarms852026年7月23日 更新

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 independence and exhaustiveness — a reviewer that fails differently from the authors, run to clean — distinct from the recursive-refinement ladder. Invoked by the team lead from the unified pre-ship gate (code-mode and /swarm:refine) after the ship steps.

中文简介正在准备中。当前显示原文说明。

DheerG/swarms852026年7月23日 更新

查看 DheerG 的全部技能

报告此技能的问题