update_doc

To audit project documentation for stale references, this Skill scans the .dev_doc directory to detect deprecated content, verify references, and compile a structured diagnostic report with remediation guidance. It uses glob, grep, and read operations to ensure alignment between code and docs.

A documentation health audit works by scanning the .dev_doc directory to verify references, detect deprecated content, and identify missing or obsolete information. This Skill then generates a comprehensive diagnostic report to guide remediation efforts and enforce documentation consistency.

Yes, you can use this documentation audit tool for any software project that contains a .dev_doc folder. It applies cross-project to enforce documentation quality and consistency without requiring manual checks or specific external dependencies.

The best way to maintain markdown documentation health is automating the audit process. This Skill scans the .dev_doc directory using glob and grep to detect obsolescence and broken references, then produces an automated diagnostic report with issue tracking for governance.

No specific external dependencies are required to run a .dev_doc directory audit. The Skill relies on standard glob, grep, and read operations to verify references and detect deprecated content, working in any repository containing the designated .dev_doc folder.

Project documentation shows obsolescence issues during audits when references become stale or deprecated over time. This Skill scans the .dev_doc directory to identify these misalignments between code and docs, producing a structured report to guide targeted remediation.