audit-docs

To audit documentation drift, cross-check every documented file against its source of truth, such as PRD, PLAN, and INDEX artifacts, to surface inconsistencies and resolve them. The process skips not-yet-built items silently while reporting actionable changes.

Documentation drift occurs when project files like PRDs, PLANS, or task DAGs fall out of sync with actual source code and tests. Auditing identifies these gaps by validating cross-references and aligning documented plans with the current repository state.

Check PRD and PLAN coverage by running a stepwise audit that validates task-DAG consistency, verifies artifact integrity, and cross-checks references across the repository. This surfaces actionable changes needed to align documentation with code and tests.

Yes, the documentation audit silently skips not-yet-built items to avoid false positives. It reports skipped files once in a consolidated summary, focusing validation strictly on existing source artifacts and their documented cross-references.

Fix CLAUDE.md drift and cross-reference inconsistencies by running an end-to-end repository health check from the root. This compares documented files against source-of-truth artifacts and provides structured guidance for aligning documentation with code.