Contradiction Detection & Divergence Classification

Classify cross-source contradictions using a three-question decision tree for synthesis pipelines.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill contradiction-detection-divergence-classification-gozonerd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Contradiction Detection & Divergence Classification
Source: https://github.com/gozonerd/shadow-ai-assessment/tree/main/.claude/skills/dmis/task_type/TT-15_Contradiction_Detection_Divergence_Classification
Command: npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill contradiction-detection-divergence-classification-gozonerd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve? When synthesizing research from multiple sources, contradictory claims can silently corrupt final outputs or block processing entirely. This Skill systematically identifies genuine cross-source disagreements and classifies each one through a structured decision tree so teams know whether to resolve, halt, or document the divergence. ## Core Features & Use Cases - Decision Tree Classification: Applies a three-question tree (factual ground truth, downstream dependency, framing vs. fact) to assign RESOLVE-BEFORE-SYNTHESIS, HALT, or DOCUMENT-ONLY verdicts per contradiction. - Structured YAML Output: Produces a contradiction classification report conforming to a defined schema, validated by an included Python script. - Accuracy Rule Enforcement: Applies 9 domain accuracy rules (ACC-001 through ACC-009) covering terminology, attribution, and thresholds. - Use Case: A research team merging interview notes and internal documentation finds conflicting deployment dates and success claims; the Skill classifies the date conflict as RESOLVE-BEFORE-SYNTHESIS and the success framing as DOCUMENT-ONLY, allowing synthesis to proceed. ## Quick Start Analyze the attached source threads for contradictions and classify each one using the TT-15 decision tree with a structured YAML report.

Frequently Asked Questions about Contradiction Detection & Divergence Classification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify contradictions between multiple research sources?

Extract all statement pairs where sources directly disagree, then apply the three-question decision tree: check for factual ground truth, assess downstream synthesis dependency, and determine if the difference is framing rather than fact. Each contradiction receives a RESOLVE-BEFORE-SYNTHESIS, HALT, or DOCUMENT-ONLY classification.

What is the difference between HALT and DOCUMENT-ONLY contradiction classifications?

HALT applies when no factual ground truth exists and downstream synthesis depends on resolving the contradiction, blocking processing. DOCUMENT-ONLY applies when the disagreement is a legitimate framing or interpretation difference, allowing both perspectives to appear in the final output.

How do I validate contradiction classification output in YAML?

Run the included validate_output.py script against your output file. It checks for required sections (contradictions_identified, decision_tree_classifications, resolution_status), verifies all three decision-tree question fields, and confirms classification values match the allowed set.

What counts as a genuine contradiction versus paraphrase variation?

A genuine contradiction involves sources making directly incompatible claims about the same fact, not differences in emphasis or wording. Marking paraphrase variations or complementary points as contradictions is a documented anti-pattern that produces false positives.

When should contradiction detection run in a synthesis pipeline?

It runs at three pipeline stages: P1 during raw input processing, P2 during foundational analysis comparisons, and P4 during final review and integration. It requires a complete thread inventory from P1 and convergence scoring from P4 as inputs.