PromptWizz
OptimizePricing
CodingintermediateClaude

Architecture Decision Record

Generates a structured Architecture Decision Record (ADR) documenting technical choices, their context, consequences, and alternatives considered.

When to use this prompt

Use this when you need to formally document a significant technical decision for your software project, creating a record that explains the reasoning to current and future team members. This template is appropriate when you want to capture not just what was decided, but why it was chosen over alternatives.

You are a software architect documenting important technical decisions.

Create an Architecture Decision Record (ADR) for:
[DECISION - e.g., "Use PostgreSQL as primary database"]

Context:
- Project type: [PROJECT]
- Team size: [SIZE]
- Constraints: [CONSTRAINTS]
- Current stack: [STACK]

Follow this structure:
1. Title (short, descriptive)
2. Status (proposed/accepted/deprecated)
3. Context (why is this decision needed?)
4. Decision (what is the decision?)
5. Consequences
   - Positive (benefits)
   - Negative (tradeoffs)
   - Neutral (implications)
6. Alternatives Considered
   - Option A: pros/cons
   - Option B: pros/cons
7. References (if applicable)

Be objective. Present facts and reasoning that would convince skeptical team members.

Free to use — the optimizer tailors this template to your exact task and target AI.

How to customize it

  • [DECISION] - State the specific technical choice you're documenting, such as selecting a database, framework, or architectural pattern
  • [PROJECT], [SIZE], [CONSTRAINTS], and [STACK] - Provide project context including the type of application, how many people are working on it, any limitations you're operating under, and existing technologies in use
  • Alternatives Considered section - List the other options you evaluated before making this decision, along with their respective advantages and disadvantages
  • References section - Add links to documentation, benchmarks, or discussions that informed the decision if they exist

What you'll get back

A formal ADR document following the seven-part structure: title, status designation, contextual explanation, the decision itself, a breakdown of positive/negative/neutral consequences, comparison of alternatives with pros and cons, and optional references. The tone will be objective and fact-based rather than promotional.

architecturedocumentationdecisions

More Coding prompts

Code Reviewer

Instructs AI to perform a comprehensive code review covering bugs, security, performance, style, and best practices with severity ratings and corrections.

Legacy Code Modernization

Generates a structured modernization plan for legacy code, including assessment, migration options, phased implementation, testing strategy, and risk management.

Regex Pattern Builder

Generates a regex pattern with detailed explanations, test cases, variations, and implementation code for your specific matching requirements.

Microservice Design

Generates a complete microservice architecture design including API endpoints, data management, infrastructure setup, and integration patterns for a specific functionality.

Make this prompt yours

PromptWizz rewrites this template around your specific task, audience, and target AI — and shows you why each change works.

Try the Optimizer Free
    llms.txt