traverse-architecture

To identify gaps in architecture decision records, you audit repository documentation to inventory existing ADRs and analyze domain coverage. This surfaces missing ADRs and generates a prioritized plan with skeleton templates to address undocumented areas.

Architecture documentation gap analysis is the process of auditing ADRs to map decision coverage across UI and API domains. It inventories existing decisions, identifies missing areas, and recommends skeleton ADR templates to fill the documentation voids.

You generate an ADR coverage report by analyzing architecture folders and indexes within your workspace. The analysis produces a structured report detailing domain statuses, related specifications, and actionable recommendations for ADR creation.

Yes, you can audit architecture decisions across both UI and API codebases simultaneously. The analysis applies to architecture indexes and developer guidance across multiple domains to surface centralized coverage statuses and related specifications.

The best way to create missing ADR templates is to perform a gap analysis on your architecture documentation. The analysis identifies coverage voids and outputs recommended skeleton ADR templates along with a prioritized plan for creation.

You need to inventory architecture decisions across multiple repositories to build a centralized view of domain coverage. This prevents isolated decisions, highlights undocumented gaps, and ensures consistent architecture governance across your codebase.