StructuredFor DevelopersTech Communication & Leadership

Architecture Decision Record (ADR) Template.

When making a significant architectural decision that future team members should understand without tracking down the original decision-maker.

ChatGPT Β· Claude Β· GeminiΒ·IntermediateΒ·~900 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
architecture-decision-record-adr-template-4.md Β· 900 words
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: Tech Communication & Leadership
- Use case: Architecture Decision Record (ADR) Template
- Source task:
  - Write a complete Architecture Decision Record (ADR) for the following decision: {{describe_the_architectural_decision_technology_choice_design_pat}}. ADR sections:
  - 1. context (what forces led to this decision?)
  - 2. decision (what was decided and by whom)
  - 3. status (Proposed / Accepted / Deprecated)
  - 4. consequences (positive and negative implications)
  - 5. alternatives considered (at least 2 other options and why they were rejected)
  - 6. compliance (how to verify the decision is being followed). Use the Nygard ADR format

# Goal
A complete ADR in Nygard format with context, decision, consequences, 2+ alternatives, and compliance verification.

# Constraints
- Produce a complete, usable first draft in one response.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
A complete ADR in Nygard format with context, decision, consequences, 2+ alternatives, and compliance verification.

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}Rolesoftware architect
{{use_case}}Your specific valuearchitecture decision record (adr) template
{{describe_the_architectural_decision_technology_choice_design_pat}}Describe the architectural decision technology choice design pattechnology choice

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When making a significant architectural decision that future team members should understand without tracking down the original decision-maker.

PRO TIP

An ADR written at decision time is 10x more valuable than one written retrospectively β€” the context and trade-offs are clearest when the decision is made.

Related prompts

Structured

Blog Post Drafting Engine

Write a complete, SEO-optimised blog post on the given topic. Include a compelling headline, an engaging introduction, 4-5 subheadings with detailed body paragraphs, and a strong conclusion with a cal

Structured

Email Newsletter Writer

Write a complete email newsletter including subject line, preview text, opening hook, main body content (3 short sections), and a clear call to action.

Structured

YouTube Video Script Writer

Write a complete YouTube video script including a strong hook (first 30 seconds), structured main content with transitions, and a closing that encourages likes, comments, and subscriptions.

Structured

LinkedIn Article Builder

Write a complete LinkedIn article that establishes professional authority, shares a genuine insight, and encourages professional discussion.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’