Architecture Decision Record
Prompt
Create an Architecture Decision Record for: Decision: {decision}. Context: {context}. Constraints: {constraints}. Options considered: {options}. Team size: {team_size}. Include: ADR number, title, status, context, decision, consequences (positive and negative), alternatives rejected with reasons, and review date.Variables
decision
context
constraints
options
team_size
About This Prompt
Create structured ADRs to document technical decisions with context, consequences, and alternatives considered.
Example Output
# ADR-0012: Use PostgreSQL over MongoDB for User Data
**Status:** Accepted
**Date:** 2026-03-25
**Deciders:** Backend team
## Context
We need a primary database for user profiles, subscriptions, and activity data. Expected scale: 100K users in year 1, 1M by year 3. Data is highly relational (users → subscriptions → payments → activity).
## Decision
Use PostgreSQL 16 as the primary database.
## Consequences
**Positive:**
- Strong relational model fits our data structure
- ACID compliance for financial transactions
- Rich ecosystem (pg_vector for future AI features, PostGIS if needed)
- Team has existing PostgreSQL expertise
**Negative:**
- Horizontal scaling requires more planning than MongoDB
- JSON queries less ergonomic than MongoDB (though JSONB is capable)
## Alternatives Rejected
1. **MongoDB** — Rejected because our data is inherently relational. Document model would require denormalization and risk data inconsistency.
2. **MySQL** — Capable but PostgreSQL offers better JSON support and extensibility.
## Review Date
September 2026 (after reaching 100K users)
Usage Tips
- Document decisions WHEN they're made not after
- Include rejected alternatives
- Keep the context section focused
- Review ADRs when assumptions change