agentleFS
Sign inStart free
yogsoth-aiyogsoth-ai/convergence/skills/disagreement-cartography/SKILL.md

disagreement-cartography

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

Map the structure of disagreement across perspectives using Policy Delphi, Argument Delphi, or SAST methods.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ensure each cluster has its strongest arguments represented

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Disagreement Cartography

Purpose: Rather than forcing convergence, map the topology of disagreement — identify clusters of opinion, the arguments supporting each cluster, and the fault lines between them. Useful for wicked problems where premature consensus would be harmful.

When to use:

  • Wicked problems with legitimate value conflicts
  • Policy questions where understanding disagreement matters more than resolving it
  • Situations where forced consensus would mask important minority views
  • Interdisciplinary disputes with incommensurable frameworks

Budget

ParameterConstraint
Rounds1–2 (mapping, not converging)
Perspectives≥4 independent
Cluster minimum≥2 distinct clusters to be useful

State Ledger

KeyTypeDescription
questionstringThe focal question or issue
perspectivesarrayList of perspective descriptions
judgmentsarrayRaw collected judgments
clustersarrayIdentified opinion clusters
argumentsarrayExtracted arguments per cluster
disagreement_mapobjectFinal visualization structure

Available Tactics

  • disagreement-mapping — Core flow: collect → cluster → extract arguments → visualize

Available SOPs

  • judgment-collection
  • cluster-analysis
  • argument-extraction
  • disagreement-visualization

Execution Guidance

  1. Frame the question to elicit diverse positions (not just ratings)
  2. Run disagreement-mapping tactic
  3. Ensure each cluster has its strongest arguments represented
  4. Produce disagreement map showing fault lines and bridging possibilities

Output Format

clusters:
  - id: <cluster_id>
    position: <summary>
    size: <number of perspectives>
    core_arguments: [...]
fault_lines:
  - between: [cluster_a, cluster_b]
    nature: <empirical/value/definitional>
bridging_possibilities: [...]

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free