ADR (Architecture Decision Record) Writer. Guides creation and maintenance of ADRs for documenting architectural decisions. Use when documenting significant technical decisions.
Skill for creating and maintaining Architecture Decision Records (ADRs) that document important technical decisions.
ADRs (Architecture Decision Records) document significant architectural decisions:
# [Decision Title]
## Status
[Proposed | Accepted | Deprecated | Superseded]
## Context
[Description of the issue motivating this decision]
## Decision
[What was decided? What will be done?]
## Consequences
### Positive
- [Positive outcome 1]
- [Positive outcome 2]
### Negative
- [Negative outcome 1]
- [Negative outcome 2]
---
## Alternatives Considered
### Alternative 1: [Name]
**Pros**: [Pros]
**Cons**: [Cons]
**Why Rejected**: [Reason]
### Alternative 2: [Name]
**Pros**: [Pros]
**Cons**: [Cons]
**Why Rejected**: [Reason]
## Notes
[Any additional notes, links, or references]
| Trigger | Example |
|---|---|
| New technology adoption | Choosing React over Vue |
| Architecture pattern | Implementing microservices |
| Database selection | PostgreSQL vs MongoDB |
| API design choice | REST vs GraphQL |
| Infrastructure decision | Kubernetes vs serverless |
| Significant refactoring | Moving to event-driven |
---
adr_number: 001