Architecture Decision Record Creator

When to Use

An architecture decision has been made (or needs to be made) and it should be documented. Typical situations:

• A technology or pattern choice has been decided — needs formal documentation
• A decision keeps getting revisited ("didn't we already decide this?") — the Groundhog Day anti-pattern
• A stakeholder asks "why did we choose X?" and nobody can answer — missing documentation
• Before implementing a significant technical change — document BEFORE building
• An existing decision needs to be superseded by a new one

Before starting, verify:

• Is there actually a DECISION to document? (If it's still an open question, use architecture-tradeoff-analyzer first to analyze trade-offs, then come back here to document the result)
• Is this decision architecturally significant? (Step 1 below helps determine this)

Context

Required Context (must have before proceeding)