arch-review

Architecture documentation drift occurs when design docs become outdated relative to source code implementation. Reviewing architecture documents against code identifies these mismatches, missing specifications, and inconsistencies, ensuring your documentation accurately reflects the current codebase state.

You can detect missing specifications in architecture docs by comparing them against the actual code implementation. This review process identifies gaps where design documents fail to describe how the source code actually works, ensuring specifications are complete and accurate.

Yes, you need LSP tools to review architecture documents against code implementation. Code navigation via LSP tools is required to accurately traverse the source codebase and compare its structure and logic against the architecture documentation for mismatches.

You should review architecture docs for code-to-doc alignment after implementing a new feature. Verifying that the architecture documentation correctly describes how the new source code actually works prevents documentation drift and maintains clarity before further changes are made.