tomevault-io Architecture Decision Record Generator
Generate an Architecture Decision Record (ADR) based on the conversation context and any architectural decisions discussed.
ADR Format
Create a markdown file with this structure:
# ADR-[NUMBER]: [TITLE]
**Date:** [YYYY-MM-DD]
**Status:** [Proposed | Accepted | Deprecated | Superseded]
**Deciders:** [Who was involved]
## Context
What is the issue that we're seeing that is motivating this decision or change?
## Decision
What is the change that we're proposing and/or doing?
## Consequences
What becomes easier or more difficult to do because of this change?
### Positive
- [Benefit 1]
- [Benefit 2]
### Negative
- [Trade-off 1]
- [Trade-off 2]
### Risks
- [Risk and mitigation]
## Alternatives Considered
### [Alternative 1]
- **Description:** What was this option?
- **Rejected because:** Why didn't we choose it?
### [Alternative 2]
- **Description:** What was this option?
- **Rejected because:** Why didn't we choose it?
## References
- [Related PR, issue, or document]
- [Relevant discussion or prior art]
Instructions
Extract from context — Use the conversation to identify:
- The problem or decision being made
- Options that were discussed
- The chosen approach and rationale
- Trade-offs acknowledged
Find the ADR location — Look for existing ADRs:
docs/adr/ordocs/decisions/adr/at project root- If none exist, suggest creating
docs/adr/
Number appropriately — Check existing ADRs and use the next number
Write concisely — ADRs should be scannable:
- Context: 2-4 sentences
- Decision: 1-2 sentences
- Consequences: Bullet points
- Alternatives: Brief, focused on why rejected
Capture the why — The decision itself ages; the reasoning stays valuable
See Also
/research— Research informs the decision; ADR captures it/review— Reviews that surface architectural decisions belong in ADRsskills/FRAMEWORKS.md— Full framework index
Converted and distributed by TomeVault — claim your Tome and manage your conversions.