Adr Writer · jonjpbm Use whenever you are about to add a new library, service, or dependency, introduce a pattern other code will need to follow, pick between two or more real options for something structural (a database tier, a state layout, a monitoring approach), or make any other call that would be expensive to reverse — stop and propose an Architecture Decision Record (ADR) before acting on it, even if the user never says the word "ADR" or asks for documentation. Also use whenever the user directly asks to write, draft, update, or supersede an ADR, or asks "should this be an ADR."
