Skill

resolve

Resolves conflicts between claims flagged by the wheat compiler. Lists unresolved conflicts, presents evidence from both sides, applies resolutions via wheat_resolve, verifies with wheat_compile.

code-quality

developer-tools

npx claudepluginhub grainulation/grainulator --plugin grainulator

Tool Access

This skill uses the workspace's default tool permissions.

Preview

The user wants to resolve a conflict between claims that the compiler couldn't auto-resolve.

SKILL.md

Similar Skills

resolve-dispute

Resolves stuck code review findings via put-up-or-concede exchange. Invoked by facilitator when findings survive arbitration without new evidence.

swarm

conflict-resolver

Analyzes git merge conflicts by type and context, proposes automated/manual resolutions, and validates fixes. Handles content, structural, semantic, and formatting issues.

devkit

challenge

Adversarially tests claims by seeking counterevidence, identifying logical fallacies, and demanding empirical proof using Wheat tools and web searches.

grainulator

Stats

Stars82

Forks6

Last CommitApr 7, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

/resolve -- Adjudicate a conflict

The user wants to resolve a conflict between claims that the compiler couldn't auto-resolve.

Arguments

$ARGUMENTS

Expected format: /resolve (show all conflicts) or /resolve <claim_id> <claim_id> (resolve specific pair)

Instructions

Get current conflicts via wheat_compile or wheat_status. List all unresolved conflicts.

If no claim IDs provided, show all conflicts and ask which to resolve. If claim IDs provided, focus on that pair.

Present both sides: Show both conflicting claims with full context — content, evidence tier, source origin, when added, and any corroborations.

Resolve: Either:

Ask the user to decide (present the tradeoff clearly)
If the user asks you to investigate, do additional research and recommend

Apply resolution via wheat_resolve:

Winner stays active
Loser becomes superseded with resolved_by set to winner's ID
Remove conflict references from conflicts_with

Run wheat_compile to verify the conflict is resolved.

Print result:

Resolved: <winner_id> over <loser_id>
Reason: <why>
Remaining conflicts: <N>

Next steps:
  /resolve            -- resolve next conflict
  /brief              -- compile if all conflicts resolved
  /blind-spot         -- check for gaps after resolution

/resolve -- Adjudicate a conflict

The user wants to resolve a conflict between claims that the compiler couldn't auto-resolve.

Arguments

$ARGUMENTS

Expected format: /resolve (show all conflicts) or /resolve <claim_id> <claim_id> (resolve specific pair)

Instructions

Get current conflicts via wheat_compile or wheat_status. List all unresolved conflicts.
If no claim IDs provided, show all conflicts and ask which to resolve. If claim IDs provided, focus on that pair.
Present both sides: Show both conflicting claims with full context — content, evidence tier, source origin, when added, and any corroborations.
Resolve: Either:
- Ask the user to decide (present the tradeoff clearly)
- If the user asks you to investigate, do additional research and recommend
Apply resolution via wheat_resolve:
- Winner stays active
- Loser becomes superseded with resolved_by set to winner's ID
- Remove conflict references from conflicts_with
Run wheat_compile to verify the conflict is resolved.

Print result:

Resolved: <winner_id> over <loser_id>
Reason: <why>
Remaining conflicts: <N>

Next steps:
  /resolve            -- resolve next conflict
  /brief              -- compile if all conflicts resolved
  /blind-spot         -- check for gaps after resolution