design-review

To review an architecture design, compare the implementation plan against existing decisions to identify gaps, evaluate trade-offs, and surface delivery risks without making repository changes.

Checking an implementation proposal for overengineering involves analyzing the technical design from a CTO perspective to validate technical choices and ensure the plan avoids unnecessary complexity before approval.

Validating a decision record requires checking the proposed design for consistency with existing DRs, component responsibilities, and architecture guidelines to find contradictions and technical risks.

Yes, you can use a design review to find missing alternatives in API and data model design by evaluating the planning discussion to confirm overlooked options are identified before implementation.

You need a technical risk assessment when finalizing implementation plans, preparing a DR, or conducting a post-meeting third-party review to identify future breaking points in performance, security, and maintainability.