adr-writer

An architecture decision needs an ADR if it is hard to reverse or likely to be questioned later. ADR worthiness checks filter out trivial implementation details that can be understood directly from code, keeping only enduring design choices.

The best way to document technology adoption is using a structured ADR. This approach drafts records with Context, Decision, Consequences, and Alternatives Considered sections to preserve the reasoning behind the choice.

To write an ADR using adr-tools conventions, draft a Michael Nygard style record. This format enforces structured sections for Context, Decision, Consequences, and Alternatives without writing usage docs.

You should not use an architecture decision record for trivial implementation details that can be understood directly from code. ADRs are reserved for choices that are hard to reverse or likely to be questioned later.

Yes, you can use an ADR to supersede older architecture decisions. This decision governance process supports technology changes and breaking changes while preserving the history of previous design choices.

An ADR worthiness check for design reviews evaluates whether a design choice is important enough to preserve. It filters out decisions understandable from code, keeping only choices that are hard to reverse or likely questioned later.