docs-coherence-audit

Audit Flintmere documentation for drift, contradictions, and broken links.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/Flintmere/flintmere --skill docs-coherence-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-coherence-audit
Source: https://github.com/Flintmere/flintmere/tree/main/.claude/skills/docs-coherence-audit
Command: npx skills add https://github.com/Flintmere/flintmere --skill docs-coherence-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit Flintmere's documentation to detect drift, contradictions, and broken links across user-facing and internal content, ensuring alignment with product behaviour and canonical sources.

Core Features & Use Cases

  • Map-driven coherence checks against docs-map.md to surface stale content, cross-doc contradictions, and broken links.
  • Drift isolation and escalation: classify findings by P0–P3 and route handoffs to writer, legal-page-draft, or engineering.
  • Unmapped-doc discovery and governance: flag unlisted docs for map expansion and governance reviews.

Quick Start

Run a full-scope coherence audit against the current docs map to produce a prioritized findings report and handoffs to the appropriate owners.

Frequently Asked Questions about docs-coherence-audit

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

FAQPage Schema
How do I audit documentation for drift and contradictions?

Run a map-driven coherence check against your docs map to surface stale content, cross-doc contradictions, and broken links, producing a prioritized report with source citations.

When do I need to run a documentation coherence audit?

Documentation coherence audits are needed during quarterly reviews, prior to major releases, or when support trends indicate user confusion, ensuring alignment with product behavior.

How do I detect broken links and stale content across internal docs?

Detect broken links and stale content by running a full-scope coherence audit against the current docs map, which isolates drift and classifies findings from P0 to P3.

Can I flag unmapped documentation for governance reviews?

Yes, you can flag unlisted documentation for map expansion and governance reviews by running an unmapped-doc discovery check during the coherence audit process.

Does the documentation audit modify files or remain read-only?

The documentation audit remains strictly read-only, producing a findings report with source citations and routing handoffs to appropriate teams rather than modifying files directly.