review-adr

To review an Architecture Decision Record comprehensively, apply a multi-pass analysis covering structural template adherence, factual accuracy, and adversarial testing of assumptions. This process validates code examples against the codebase and challenges reasoning to ensure technical soundness.

Adversarial testing in architecture documentation is an analytical lens that challenges the assumptions and reasoning within an Architecture Decision Record. It actively uncovers potential flaws in design choices to prevent the adoption of harmful technical decisions.

You validate code examples in a technical decision record by running a dedicated verification pass against the actual codebase. This checks factual accuracy, ensures the proposed implementation plan is viable, and prevents costly mistakes before merging.

You need a formal review process for ADRs before merging critical architectural choices, such as introducing a new language feature. It ensures institutional knowledge is maintained, reasoning is sound, and flawed design choices are caught early.

Yes, this ADR review approach works without external dependencies. It operates as a standalone skill using internal scripts and references to perform structural validation, reasoning checks, and codebase verification directly on your documentation.