Architecture Decision Record

Overview

Produce rigorous Architecture Decision Records (ADRs) that capture the context, options, tradeoffs, and rationale behind significant technical decisions. ADRs are durable artifacts — they explain why a decision was made so that future teams don't relitigate settled questions.

When to Use

• Choosing a technology, framework, or platform
• Evaluating build vs buy
• Selecting an architectural pattern (monolith vs microservices, event-driven vs request-response, etc.)
• Making infrastructure decisions (cloud provider, database, messaging system)
• Any technical decision that affects multiple teams, is expensive to reverse, or will be questioned later

Instructions

Step 1: Define the Decision

Ask the user for (skip what's already provided):