create-adr

To document architecture decisions, you can generate an Architecture Decision Record that captures context, alternatives, rationale, and consequences for system design choices and technology selections. This ensures trade-offs remain traceable.

An Architecture Decision Record is a structured document that captures context, alternatives, rationale, and consequences for major architectural choices. You need one when making system design decisions or technology selections to maintain traceable living documentation.

To write an ADR comparing technology alternatives, analyze the decision context to surface goals and constraints, then identify alternatives and document the rationale for tradeoffs. This produces a complete decision record with traceable notes.

Yes, you can generate a complete ADR using a standard template for system design pattern selections. The template structures your context, decision, alternatives, rationale, and consequences into living documentation that remains reviewable over time.

Architecture Decision Records capture context and consequences but require manual maintenance to serve as living documentation. They are best suited for major architectural choices and pattern trade-offs across teams, rather than minor implementation details.