incoherence

Detect contradictions between documentation, specifications, and code.

898|134|Updated Jul 28, 2025

Search Tags:#documentation #consistency #reconciliation #code #incoherence

Ready to run

npx skills add https://github.com/solatis/claude-config --skill incoherence

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incoherence
Source: https://github.com/solatis/claude-config/tree/main/skills/incoherence
Command: npx skills add https://github.com/solatis/claude-config --skill incoherence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Incoherence detection and reconciliation to resolve contradictions between docs, specs, and implementation, with a structured workflow to apply user resolutions.

Core Features & Use Cases

Parallel exploration & reconciliation: Detect inconsistencies across multiple dimensions.
Dimension catalog: Map potential inconsistencies to concrete focus areas.
Reconciliation workflow: Apply user-provided resolutions and recheck outcomes.

Quick Start

Start the detection workflow: python3 scripts/incoherence.py --step-number 1 --total-steps 22 --thoughts "Analyzing project X"

Frequently Asked Questions about incoherence

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

FAQPage Schema

How do I detect inconsistencies between documentation and code?▼

Documentation-code incoherence detection identifies contradictions, ambiguities, and gaps across docs, specifications, and implementation through a structured 22-step workflow that maps inconsistencies across multiple dimensions and produces a reconciliation report.

What's the best way to reconcile conflicting documentation and source code?▼

Use a coordinated detection and reconciliation workflow that explores inconsistencies in parallel, catalogs problematic dimensions, and applies user-provided resolutions iteratively to ensure updated artifacts remain coherent across all project layers.

Can I automate checking for specification-code mismatches in my project?▼

Yes, the Python-based workflow accepts a user-specified report filename and coordinates parent and sub-agent phases to automatically detect mismatches, generate structured issue reports, and apply reconciliation—supporting idempotent re-runs as specs and code evolve.

What input formats and project structure do I need for incoherence detection?▼

The workflow applies to software projects containing documentation files, formal specifications, and source code; it accepts a report filename parameter and outputs a structured issue-resolution report with updated, internally consistent artifacts.

How does the reconciliation workflow handle contradictions between multiple documentation and code sources?▼

The 22-step process maps potential inconsistencies across a dimension catalog, explores them in parallel, and synthesizes resolutions that coordinate parent and sub-agent phases to recheck outcomes and ensure all artifacts stay synchronized.

What limitations should I consider when using documentation-code reconciliation?▼

The workflow requires explicit user resolutions for detected incoherence; it works best on projects with distinct documentation, specifications, and implementation layers, and relies on user-provided report filenames to structure output consistently.