adr-template

name	ADR Template
department	chronicler
description	Architecture Decision Record creation with options analysis and review triggers
version	1
triggers	["ADR","decision","architecture decision","rationale","decision record","design decision","tradeoff"]

ADR Template

Purpose

Create Architecture Decision Records that capture the context, options considered, decision rationale, and consequences of significant technical choices. Produces structured ADR documents that serve as the institutional memory of the project.

Inputs

• The architectural question or decision being made
• Current system context and constraints
• Stakeholder concerns and priorities
• Related previous decisions (existing ADRs)

Process

Step 1: Identify the Decision to Record

Clearly frame the architectural question:

• What specific question was (or needs to be) resolved?
• Why is this decision significant enough to record? (Costly to change, cross-cutting impact, team disagreement)
• What is the scope of this decision? (Single service, full system, team process)
• Assign a sequential ADR number and descriptive title

Step 2: Describe Context

Document the forces at play:

• What is the current state of the system relevant to this decision?
• What constraints exist? (Technical: language, framework, infrastructure. Business: timeline, budget, team size)
• What requirements drive this decision? (Functional, non-functional, compliance)
• What assumptions are being made?
• Reference related ADRs that provide context or are affected by this decision

Step 3: Enumerate Options Considered

List at least 2-3 alternatives, including "do nothing":

• Option A: [Name] — Brief description of the approach
• Option B: [Name] — Brief description of the approach
• Option C: Do nothing / Status quo — What happens if no change is made
• For each option, provide enough detail for a reader to understand the approach without external context

Step 4: Evaluate Each Option

Analyze tradeoffs systematically:

• Pros: What does this option do well? Alignment with principles, simplicity, performance
• Cons: What are the downsides? Complexity, risk, learning curve, migration effort
• Risks: What could go wrong? Scaling issues, vendor lock-in, maintenance burden
• Effort: Rough implementation effort (T-shirt size: S/M/L/XL)
• Alignment: How well does this option align with architectural principles and team capabilities?

Step 5: Document the Decision

State the chosen option and core rationale:

• Which option was selected?
• What was the primary reason for choosing it? (Not "it's the best" — the specific tradeoff that tipped the balance)
• Was this decision unanimous or contentious? Note dissenting opinions if applicable
• What conditions would make this the wrong decision? (Helps future readers know when to revisit)

Step 6: Specify Consequences

Detail what follows from this decision:

• What becomes easier: Capabilities enabled, patterns simplified, workflows improved
• What becomes harder: Constraints introduced, options foreclosed, complexity added
• New constraints: What must all future development respect because of this decision?
• Technical debt accepted: What shortcuts or imperfections are knowingly accepted?
• Follow-up work: What tasks, migrations, or changes are needed to implement this decision?

Step 7: Define Review Triggers

Specify when this decision should be revisited:

• Scale thresholds: "Revisit if traffic exceeds X or data grows beyond Y"
• Technology changes: "Revisit if [framework/service] releases [capability]"
• Team changes: "Revisit if team grows beyond N engineers or splits into multiple teams"
• Time-based: "Review after 12 months regardless of other triggers"
• Pain indicators: "Revisit if [specific friction point] becomes a recurring issue"

Output Format

# ADR-[NNN]: [Descriptive Title]

**Status**: [Proposed | Accepted | Deprecated | Superseded by ADR-NNN]
**Date**: [YYYY-MM-DD]
**Deciders**: [Who was involved in the decision]

## Context

[What is the situation? What forces are at play? What constraints exist?]

[Reference related ADRs: ADR-NNN, ADR-NNN]

## Decision

We will [chosen approach].

[Core rationale — the specific tradeoff that decided it.]

## Consequences

### What becomes easier
- [Consequence 1]
- [Consequence 2]

### What becomes harder
- [Consequence 1]
- [Consequence 2]

### Technical debt accepted
- [Debt item and why it's acceptable for now]

## Alternatives Considered

### Option A: [Name]
[Description]
- **Pros**: [list]
- **Cons**: [list]
- **Why not**: [specific reason this was rejected]

### Option B: [Name]
[Description]
- **Pros**: [list]
- **Cons**: [list]
- **Why not**: [specific reason this was rejected]

### Option C: Do Nothing
[What happens if we don't act]
- **Pros**: No effort, no risk of change
- **Cons**: [specific problems that persist or worsen]
- **Why not**: [why inaction is unacceptable]

## Review Triggers

- [ ] [Scale threshold]: Revisit if [condition]
- [ ] [Technology change]: Revisit if [condition]
- [ ] [Team change]: Revisit if [condition]
- [ ] [Time-based]: Review by [date]

Quality Checks

• Decision is framed as a clear architectural question with defined scope
• Context captures constraints, assumptions, and related decisions
• At least 3 options are evaluated including "do nothing"
• Each option has pros, cons, risks, and effort assessed
• Decision rationale explains the specific tradeoff, not just "it's better"
• Consequences cover both what becomes easier and harder
• Review triggers define concrete conditions for revisiting the decision
• ADR is self-contained — a reader can understand it without external context

Evolution Notes