eng-architecture-decision

Use structured Architecture Decision Records to capture context, criteria weights, option evaluations, and final recommendations. This generates weighted comparison matrices, lists pros and cons, and enumerates risks with mitigations to formalize technology selection.

Create an Architecture Decision Record by building criteria with weights and computing option scores. This produces a weighted comparison matrix that quantifies trade-offs across migration cost, performance, and organizational fit for engineering teams.

Yes, the process reads project docs and org priorities, searches prior ADRs, and identifies affected products and constraints. It uses this context-aware framing to enforce decision gates and generate recommendations for irreversible and reversible design choices.

Enumerate top risks per option alongside their mitigations within an Architecture Decision Record. This risk and governance framing balances migration cost, performance, and organizational fit when deciding between databases, message buses, or deployment strategies.

Architecture Decision Records are saved locally under docs/adrs and a one-line summary is logged to memory. This ensures engineering teams can track irreversible and reversible design choices across projects and products.

You need a decision record when balancing migration cost, performance, and organizational fit across projects. It applies to engineering teams documenting system architecture choices, migrations, technology selections, and RFC-level design decisions.