incoherence
Detect and resolve incoherence in documentation, code, specs vs implementation. Includes reconciliation phase for applying user-provided resolutions.
When & Why to Use This Skill
The Incoherence Detector is a specialized Claude skill designed to synchronize your technical ecosystem by identifying and resolving discrepancies between documentation, source code, and design specifications. It automates the tedious process of cross-referencing implementation details with written requirements, ensuring that your codebase remains accurate, maintainable, and aligned with its intended architecture through a structured 21-step reconciliation workflow.
Use Cases
- 1. Documentation-Code Synchronization: Automatically detect and fix outdated READMEs, API docs, or comments that no longer reflect the actual behavior of the code.
- 2. Specification Compliance: Verify that the final implementation matches the original technical specifications or PRDs (Product Requirement Documents) to ensure feature accuracy.
- 3. Technical Debt Reduction: Identify 'logic drift' in legacy codebases where implementation has evolved away from the original documentation over time.
- 4. Automated Code Audits: Streamline the code review process by highlighting inconsistencies in logic, naming conventions, and architectural patterns across different files.
| name | incoherence |
|---|---|
| description | Detect and resolve incoherence in documentation, code, specs vs implementation. |
Incoherence Detector
When this skill activates, IMMEDIATELY invoke the script. The script IS the workflow.
Invocation
| Argument | Required | Description |
|---|---|---|
--step-number |
Yes | Current step (1-21) |
--total-steps |
Yes | Always 21 |
--thoughts |
Yes | Accumulated state from all previous steps |
Do NOT explore or detect first. Run the script and follow its output.
Workflow Phases
- Detection (steps 1-12): Survey codebase, explore dimensions, verify candidates
- Resolution (steps 13-15): Present issues via AskUserQuestion, collect user decisions
- Application (steps 16-21): Apply resolutions, present final report
Resolution is interactive - user answers structured questions inline. No manual file editing required.