lidr-adr

Generate Architecture Decision Records (ADRs) in MADR format to document significant technical decisions with context, alternatives, trade-offs, and rationale. Domain-agnostic — works for any technology stack, architecture style, or industry vertical. Use for hard-to-reverse decisions, decisions affecting multiple teams, significant trade-off choices, extensively debated options. ALWAYS use when documenting significant architectural decisions that are costly to reverse. Essential when a technical decision needs to be preserved so future team members understand the why. Always use when choosing a database/framework/cloud provider, always use when a decision was debated and needs documentation to avoid re-debating. Do NOT use for trivial reversible decisions, decisions already in tech-stack rules, or temporary PoC decisions. Triggers on "architecture decision", "ADR", "technical decision record", "document decision", "why did we choose", "decision record", "technical trade-off". Content authored in English (MAD

By LIDR-IT schedule Updated 6/14/2026