[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fh4Jl_82Xv2mUGC8pzjxapL3JkWrSgn3X6tKMY6VKb0c":3},{"slug":4,"title":5,"seoTitle":6,"seoDescription":7,"h1":8,"intro":9,"category":10,"template":11,"inputs":12,"promptTemplate":38,"outputFormat":39,"faq":40,"relatedSlugs":56,"seoSections":62},"architecture-decision-record-generator","Architecture Decision Record Generator","AI ADR Generator | Document Architecture Decisions Easily","Generate Architecture Decision Records documenting technical choices, trade-offs, and rationale. Create structured ADRs that preserve institutional.","AI Architecture Decision Record Generator","Describe a technical decision and get a well-structured Architecture Decision Record with clear context, decision rationale, alternatives considered, trade-offs, and consequences — preserving the why behind your architecture for future developers.","developer","form",[13,20,24,29],{"name":14,"label":15,"type":16,"placeholder":17,"required":18,"maxLength":19},"decision","Decision Made","textarea","e.g., We will use PostgreSQL instead of MongoDB for the user activity feed because we need strong consistency for billing-related events",true,1000,{"name":21,"label":22,"type":16,"placeholder":23,"required":18,"maxLength":19},"context","Context & Constraints","e.g., High write volume (10k events\u002Fsec), must support time-range queries, team has SQL expertise, budget constraints limit managed services",{"name":25,"label":26,"type":16,"placeholder":27,"maxLength":28},"alternatives","Alternatives Considered","e.g., MongoDB with TTL indexes, DynamoDB with GSIs, TimescaleDB, ClickHouse",500,{"name":30,"label":31,"type":32,"options":33,"default":34},"adrFormat","ADR Format","select",[34,35,36,37],"Michael Nygard format","MADR (Markdown ADR)","Y-Statements","Lightweight","Generate an Architecture Decision Record in {{adrFormat}} format. Decision: {{decision}}. Context: {{context}}. Alternatives: {{alternatives}}. Include clear status, context with problem statement, decision statement, detailed rationale with trade-offs for each alternative, consequences (positive and negative), and follow-up actions or review triggers.","markdown",[41,44,47,50,53],{"question":42,"answer":43},"What is an Architecture Decision Record?","An ADR is a short document that captures a significant architectural decision along with its context, rationale, and consequences. ADRs create an immutable log of why decisions were made, preventing the common problem where teams revisit settled decisions because no one remembers the original reasoning. They are typically stored alongside the code in an adr\u002F directory.",{"question":45,"answer":46},"What ADR formats does the generator support?","We support the Michael Nygard format with Status, Context, Decision, and Consequences sections. The MADR format adds Considered Options with detailed pros and cons for each. Y-Statements provide a compact single-sentence decision format. The Lightweight format is a minimal template for smaller decisions. Each format follows its respective community convention.",{"question":48,"answer":49},"When should I create an ADR?","Create an ADR for decisions that are hard to reverse, affect multiple team members, involve trade-offs between competing concerns, or will be questioned by future developers. Examples include choosing a database, selecting an authentication approach, deciding on an API versioning strategy, or picking a deployment architecture. If you considered alternatives, it is worth recording.",{"question":51,"answer":52},"How detailed should the alternatives section be?","Each alternative should include a brief description, its key advantages, its main drawbacks, and why it was ultimately not chosen. This prevents future team members from re-proposing the same alternatives and shows that the decision was made thoughtfully. Include quantitative comparisons like benchmark results or cost estimates when available.",{"question":54,"answer":55},"What happens when a decision needs to be revisited?","ADRs are immutable — you never edit a past ADR. Instead, create a new ADR that supersedes the old one, referencing it and explaining what changed in the context that requires a new decision. The old ADR's status changes to Superseded with a link to the replacement. This preserves the full history of your architecture's evolution.",[57,58,59,60,61],"technical-spec-generator","readme-generator","pull-request-description-generator","changelog-dev-generator","blog-post-title-generator",[63,66],{"title":64,"content":65},"Preserve the Why Behind Your Architecture","Code shows what a system does, but not why it was built that way. Architecture Decision Records capture the context, constraints, and trade-offs that led to each significant technical choice. When a new team member asks why you chose PostgreSQL over MongoDB, or why the API uses REST instead of GraphQL, the ADR has the answer.",{"title":67,"content":68},"Stop Relitigating Settled Decisions","Without documented decisions, teams waste time revisiting choices that were already carefully evaluated. Our generator produces comprehensive ADRs that document the alternatives considered, the evaluation criteria, and the rationale for the chosen approach. Future discussions can build on this foundation rather than starting from scratch."]