maintain-architecture-map

Architecture documentation stays synchronized by scanning the codebase structure to automatically generate and populate sections of ARCHITECTURE_MAP.md, including module maps, entry points, and data flows.

Documenting module dependencies and data flows for a design review is best handled by generating an ARCHITECTURE_MAP.md that cross-links module guides and data-flow diagrams. This ensures system structure is communicated clearly to stakeholders.

Yes, you can automatically generate an architecture map for onboarding sessions. The process scans repository-wide module structures and dependencies to populate ARCHITECTURE_MAP.md, ensuring new team members understand the system structure clearly.

Yes, this approach works for maintaining documentation across a repository with multiple modules. It applies template-driven documentation to refresh the System Overview, Three-Layer Architecture, and Module Guide sections across the entire repository.

You need to regenerate the architecture map when adding new modules, refactoring the architecture, or preparing for a design review. Running the architecture scan after code changes ensures ARCHITECTURE_MAP.md stays up-to-date.