common-doc-audit-k

You can audit repository documentation by running a structured process that verifies living docs, ARCHITECTURE.md, and design-docs to catch drift, broken cross-links, and missing sections. This skill provides both post-build verifiers and periodic tree audits to sustain documentation health.

Stale documentation misleads users and degrades trust when living docs no longer reflect the latest build or code changes. You can check for this by enforcing post-build verification to confirm ARCHITECTURE.md alignment and living doc freshness across the repository.

The best way to verify cross-link integrity and diagram accuracy is to periodically audit the entire design-docs tree using a dedicated gardener process that catches broken links and ensures diagrams, plans, and modules stay in sync with code.

Yes, you can run a living doc freshness check automatically after a build. The skill acts as a verifier post-build to confirm that living docs reflect the latest build output and that ARCHITECTURE.md is up to date.

You need to escalate documentation drift when periodic audits identify broken cross-links or outdated plan statuses. The skill provides clear escalation and remediation guidance to help correct diagram inaccuracies and living doc staleness across the full doc tree.