Skip to content
Log in

Architecture Decision Record

Writes an ADR that captures why, including the options rejected and what would make you revisit it.

0

Share this prompt

Free — no card needed

Create a free account

to open Architecture Decision Record — and the other 364 prompts across 21 categories.

We store your email address to send these. We never sell it or pass it to advertisers. Withdraw at any time. Privacy Policy.

Already have an account?

CategoryCodingForDevelopers, FoundersTested onClaudeChatGPT

Running it, start to finish

  1. Capture the constraints while they are still true and remembered.
  2. Write the rejected options at their strongest.
  3. Set a concrete revisit condition before marking it accepted.

What you get back

The output this produces, every time.

  • Records the constraints that were true at the time, which is the part that ages best and is usually thinnest.
  • Steelmans the rejected options, so a future reader trusts the analysis.
  • Names the conditions for revisiting, without which the decision becomes permanent by default.

Getting better results

Where this usually goes wrong, and how to avoid it.

  • Write the constraints in full. Team size, deadline, what already existed. A future reader judging the decision without them will conclude it was wrong.
  • Do not dismiss alternatives quickly. A one-clause rejection reads as though the option was not seriously considered, and invites someone to reconsider it from scratch.
  • Fill in revisit-when. It is the difference between a decision and a permanent constraint nobody remembers choosing.

More Coding prompts

All Coding

Written for The AI University. Every prompt in this library is original work — authored, tested and revised here, not collected from elsewhere. 365 of them, free with an account.