update-project-docs

Project documentation drift is fixed by scanning and cross-referencing docs like READMEs and task lists against the actual filesystem state. This process updates outdated statuses, prunes stale references, and appends timestamped learnings to keep knowledge bases truthful.

A documentation audit is automated by enforcing a repeatable process: inventory existing docs, read their content, cross-reference them with the filesystem, fix discrepancies, and timestamp updates. This ensures project state is accurately reflected across all knowledge base files.

You should run a documentation update after completing work such as milestones, sprint finishes, or team reorganizations. These events change the actual project state, requiring a scan to reconcile file trees, status lines, and team rosters in the documentation.

To update a README and team roster after a reorganization, inventory the current docs, cross-reference them with the filesystem, and fix discrepancies. This process reflects new team members, updates file trees, and consolidates outdated entries to maintain an accurate knowledge base.

No, this documentation hygiene process requires no external dependencies. It operates autonomously to scan project files, cross-reference filesystem state, and apply updates to project management docs without needing additional components or libraries.