garden-docs

A documentation drift audit cross-checks in-scope markdown files like AGENTS.md against current code to surface dead references, layout-claim drift, and contradictions. It generates a citation-backed punch list with actionable remediation steps and suggested owners for each file.

Documentation drift happens when markdown claims become outdated relative to current code. An audit identifies stale repo docs by inventorying in-scope markdown files, cross-checking them against the codebase, and surfacing dead references, layout-claim drift, and cross-document contradictions.

Yes, you can generate a punch list for documentation bloat by running a focused audit across in-scope markdown files. The audit evaluates files for redundancies and outdated claims, producing a citation-backed punch list with actionable remediation steps and suggested owners.

The documentation audit works with specific repository layouts by applying checks across in-scope markdown files including AGENTS.md, methodology, operations, platform, and workspace docs. It identifies layout-claim drift, dead references, and contradictions while honoring documented procedures and anti-patterns.

The best way to find dead references in repository markdown files is to run a documentation audit that cross-checks in-scope markdown against current code. The audit surfaces dead references and cross-document contradictions, producing a citation-backed punch list with actionable remediation steps.