update-repo-reference

To keep repository documentation in sync with code changes, you can run a synchronization process that updates reference files like current-state.md and roadmap.md to reflect new skills and behavior changes, preventing outdated information.

Documentation drift occurs when reference files become inconsistent with actual implementation. Sanity checks identify this drift by validating the accuracy of files like current-state.md and backlog.md against recent OAT changes and conventions.

To update current-state.md and roadmap.md after adding a new skill, execute a documentation synchronization task that scans the .agents/skills/ directory and propagates the new skill status into the OAT reference docs.

Updating OAT reference documentation requires no external dependencies. The process operates directly on repository files to validate accuracy and synchronize conventions without additional packages.

The best way to maintain backlog.md accuracy during active development is to synchronize it regularly with implementation changes, ensuring updated behaviors and conventions are validated through sanity checks.