ADR (Architecture Decision Record) Drafter
Turns an architectural choice into a concise ADR with context, options, trade-offs, and consequences — the artifact teams actually need later.
Draft an ADR (Michael Nygard format) for the decision: {{DECISION}}. Context: {{problem, constraints, options already considered, deadlines, team skills}}. Write: - Title + status (Proposed) + date. - Context: facts and forces (scale, cost, team familiarity, existing systems, compliance). Use bulleted, verifiable statements; separate facts from preferences. - Considered options (at least 3, including "do nothing") with a comparison table scored against: correctness guarantees, operational complexity, cost, scalability, migration effort, ecosystem/maturity, vendor lock-in, and team learning curve. - Decision: the single chosen option and the DECISIVE reasons (reference the table). - Consequences: positive, negative, and risks created; what becomes easier/harder; what monitoring will tell us if the choice was wrong; reversal cost and trigger conditions for revisiting (review date). Keep it to ~1.5 pages; no vendor marketing language; cite load/cost numbers where possible. ================================================================================
自动翻译
自动翻译中…