Software Architecture Decision Record Generator

Writes an ADR (context, options considered, decision, consequences) for a technical decision you've already made or are weighing.

Software Developmentintermediate10 minNo ratings yet

When to use this

Use to document a decision for future maintainers, or to force rigor while still deciding between options.

Prompt template

You are writing an Architecture Decision Record. Decision to document: {{decision_title}}
Context/constraints: {{context}}
Options considered: {{options_considered}}
Chosen option (if already decided; otherwise say 'undecided'): {{chosen_option}}

Write an ADR with:
1. Context (the forces at play: technical, business, team constraints).
2. Options considered, with a genuine tradeoff for each (not a strawman).
3. Decision (or, if undecided, a recommendation with reasoning).
4. Consequences, including at least one negative/accepted tradeoff of the chosen option.

Customize

Decision to document is required

Context/constraints is required

Options considered is required

Preview

You are writing an Architecture Decision Record. Decision to document: {{decision_title}} missing
Context/constraints: {{context}} missing
Options considered: {{options_considered}} missing
Chosen option (if already decided; otherwise say 'undecided'): undecided

Write an ADR with:
1. Context (the forces at play: technical, business, team constraints).
2. Options considered, with a genuine tradeoff for each (not a strawman).
3. Decision (or, if undecided, a recommendation with reasoning).
4. Consequences, including at least one negative/accepted tradeoff of the chosen option.

Usage instructions

List real options you actually weighed, including the one you didn't pick; an ADR with only one option considered usually means the tradeoffs weren't examined yet.

Example output

An ADR documenting the cPanel single-process constraint as context, genuine tradeoffs for each option (Postgres costs money and adds an external dependency; staying JSON-file-based can't support filtering/pagination), the SQLite decision, and a named consequence: migrating to multiple worker processes later will require a database change.

Limitations

Reflects only the context and options you provide; it cannot independently verify technical claims about your infrastructure.

Rate this prompt

Not yet rated