Architecture decision record
Document a consequential technical choice with steelmanned options and reversal signals.
Read this prompt as Markdown or plain text
When to use it
Ranked drivers and reconsideration triggers turn an ADR from a retrospective justification into a reversible, evidence-aware decision tool.
Prompt
Create an Architecture Decision Record for [DECISION]. Do not implement the decision. First inspect the repository and supplied context so the record reflects the actual system. Separate confirmed facts from assumptions. Write the ADR with: - Title, date, status, owners, and decision scope - Context: the forces creating the decision, current constraints, and why a decision is needed now - Decision drivers ranked by importance - At least two viable options plus “do nothing” when meaningful - A steelman of each option, including operational, security, privacy, performance, cost, migration, and team-skill effects - Decision and concise rationale tied directly to the ranked drivers - Positive and negative consequences, including new failure modes and long-term maintenance - Implementation and migration outline, compatibility needs, and rollback/reversal path - Validation plan with measurable signals and review date - Reconsideration triggers: the evidence or changed constraints that should reopen the decision - References to relevant files, issues, benchmarks, incidents, or documentation Do not fabricate benchmark results or consensus. If the decision cannot responsibly be made from current evidence, set status to Proposed and list the minimum experiments or stakeholder decisions required.
Adapt it to your task
Condensed and made repository-grounded from GitHub Awesome Copilot's ADR Generator.
Third-party prompt. Source review does not establish benchmark performance or guarantee an outcome.
Source and license
Contributor: @askpt. Repository: github/awesome-copilot.
License: MIT. Pinned commit: b95e24caae4f25c5985f8527fd092ccfed039c36.
Review: source-reviewed, . Compared with the commit-pinned source and adapted into a tool-neutral, copy/paste request. This is a non-visual task, so no output artifact is required.