docs-writer

Documentation accuracy is maintained by auditing repository files to verify version numbers, agent counts, and structural references. This process aligns project details with the current state, reducing maintenance errors and confusion during releases.

Project documentation becomes outdated when version info, entity counts, and structural references are not regularly verified. Staleness leads to inefficiency among users and developers, making onboarding and release preparation prone to errors.

The best way to audit documentation staleness is to check for outdated version information, broken links, and inconsistent entity counts. Reviewing these elements ensures your repository docs are error-free and current for new team members.

You can update repository documentation by asking an AI to review your files and align them with the current project state. This includes proofreading for technical correctness, updating version numbers, and verifying structural references.

Yes, you can check for broken links and inconsistent entity counts as part of a documentation staleness audit. This verifies that structural references and project details like agent and skill counts are fully accurate and fresh.

You need to update documentation for structural references and entity counts when onboarding new team members or preparing releases. Regular updates maintain clarity, verify project details, and reduce errors during repository maintenance.