contradiction-map

Contradiction Map — Find Where Understanding Lives

The most valuable understanding lives where credible sources disagree. Consensus is comfortable; contradiction is where the real questions are — and the angle nobody covered is often the gap in the entire field. This skill maps disagreement, agreement, and blind spots across any set of viewpoints. It's STORM Phase 2, usable on its own.

When to Use vs. storm-research

Use this directly when you already have the viewpoints to compare:

• A prior multi-perspective-scan left a workspace at .storm/{slug}/
• The user has several documents, reports, or articles to reconcile
• The user pastes a handful of competing positions and wants them mapped

For generating the perspectives first, then mapping them, use multi-perspective-scan or the full storm-research.

Workflow

Step 1 — Locate the Inputs

Determine what's being compared:

• STORM workspace: if .storm/{slug}/ exists with perspective files, use those.
• Files/documents: the user names paths or a directory — gather the relevant files.
• Pasted viewpoints: the positions are in the conversation — you'll pass them to the agent directly in the prompt.

If the source is unclear, ask one question to pin it down. Establish (or derive) a topic label and, for file-based runs, a workspace .storm/{slug}/ for the output (mkdir -p it).

Step 2 — Spawn the Contradiction Mapper

Launch the contradiction-mapper agent with one Task call:

"Topic: {topic}. Workspace: .storm/{slug}/. Inputs: {list of files, OR the pasted viewpoints inline}. Read every input in full and write .storm/{slug}/contradiction-map.md per your output contract — major contradictions with verdicts, the reliable core of agreement, and the blind spots none of the inputs addressed."

For purely pasted viewpoints with no workspace, instruct the agent to return the map inline instead of writing a file.

Step 3 — Present the Map

Surface the highlights and point to the full artifact: