architecture-review

Architecture review evaluates stories or systems against eight dimensions like security, scalability, and observability to surface cross-cutting risks early. It requires reading your ARCHITECTURE_DESIGN.md and ADRs before generating per-dimension status, findings, and recommendations.

An architecture review based on ADR governance maps proposed changes to affected components by enforcing a read-through of architecture decision records. This ensures traceability and produces dimension-scoped findings for reliability, performance, and tech debt risks.

Run a system-level review by loading your ARCHITECTURE_DESIGN.md sections and all ADRs. The evaluation generates a per-dimension status of OK, Warning, or Kritisch, detailing findings and concrete recommendations for backlog issues.

Yes, optional dimension add-ons for Privacy/GDPR, Cost Efficiency, Signal Quality, and Compliance can be activated. These dimensions are loaded based on your bootstrap configuration alongside the standard eight architecture dimensions.

Yes, an enforced documentation-first workflow requires reading ARCHITECTURE_DESIGN.md sections one through eight plus all ADRs before evaluation. This prevents architecture review from becoming a vague gut check and ensures traceability.

Avoid this approach if your project lacks an ARCHITECTURE_DESIGN.md or existing ADRs. The evaluation strictly enforces a read-through of these documents to map changes and produce dimension-scoped findings, making it unsuitable for undocumented systems.