docs-review

Documentation consistency is enforced by cross-referencing definitions, relationships, and update currency across ADRs, runbooks, READMEs, and architecture diagrams to detect and resolve contradictions. This ensures repository artifacts accurately reflect the current system design and operating procedures.

The best way to verify ADR and README coverage is to check that required artifacts exist and remain current, ensuring ADRs document significant decisions and READMEs reflect updated setup and architecture diagrams. This prevents outdated claims and missing operational context.

To audit markdown files and runbooks for outdated information during maintenance, cross-reference definitions and configurations across architecture and constraint artifacts. This verifies mutual consistency and applies conditional edits only when actual contradictions or outdated information are found.

Yes, validating AGENTS.md context alignment checks that subdirectory context aligns with global invariants without overwriting correct documentation. Conditional edits are applied exclusively when actual contradictions or outdated information are discovered, preserving accurate existing files.

A repository-wide documentation audit is needed after architectural decisions, during maintenance, or when encountering complex code requiring verification of documentation accuracy. It enforces mutual consistency and verifies ADR, runbook, README, and AGENTS.md coverage across the repository.