adr-writer

An architecture decision record (ADR) captures context, rationale, alternatives, and consequences for technical choices. You need an ADR when making component boundary, technology selection, or process decisions to prevent knowledge gaps during future maintenance, onboarding, and audits.

To document architecture decisions, generate ADR documents with clear Context, Decision, Alternatives, and Consequences sections. Use guided elicitation prompts to capture constraints and stakeholders, then apply alternatives analysis and scoring guidance to evaluate complex trade-offs and rejection reasons.

Manage the ADR lifecycle by applying sequential numbering (ADR-001 …) and status lifecycle metadata (Proposed, Accepted, Deprecated, Superseded). Follow included guidance for supersession and immutability to track decision status across component boundaries and technology selections over time.

The context section of an architecture decision record should include constraints, stakeholders, and triggers captured through elicitation prompts. Document concrete rejection reasons for considered alternatives and projected consequences to ensure reviewers understand why a choice was made months or years later.

Yes, the ADR template supports governance and audit requirements by producing numbered, status-tracked documents with metadata. It captures reference-backed best practices, alternatives analysis frameworks, and context-capture techniques to ensure decisions are reproducible and discoverable for rigorous review.

The best way to track technology selection rationale is to create numbered ADR documents with explicit criteria, migration considerations, and consequences. Record the decision, alternatives considered, and lifecycle status to provide reproducible, discoverable context for future onboarding and audits.