Architecture decision record
Compares technical options against your constraints and writes the ADR with consequences.
Use it when
Choosing a database, queue, framework or service boundary.
What you fill in
- decision The technical decision
- options Options under consideration
- constraints Scale, team skills, budget, latency, compliance
The prompt
Write an architecture decision record. Decision: decision Options: options Constraints: constraints Sections: context; decision drivers (ranked); each option with pros, cons and fit to each driver (table); the decision; consequences (good, bad, and what becomes harder later); how to reverse it if wrong and what that would cost; and a spike to de-risk the choice in under 3 days. Be specific about numbers (throughput, cost per month, latency) where the constraints allow. Before you answer, check your draft against every instruction above and fix anything that misses.
Why it works
- Ranks drivers so trade-offs are explicit.
- Records consequences, including what gets harder.
- Prices reversal up front.