adr
The ADR skill helps you record major architectural choices in a structured format that captures the reasoning behind decisions, not just the outcome. It stores numbered records in your project's docs folder and guides you through context, trade-offs, and consequences so your team can understand why decisions were made.
The ADR skill documents significant architectural decisions with context, options, and consequences for institutional knowledge.
AI-generated summary based on this skill's SKILL.md
Install
irahardianto/awesome-agv/adr · repository language: JavaScript
git clone https://github.com/irahardianto/awesome-agv
cp -r awesome-agv/.agents/skills/adr ~/.claude/skills/adrnpx skillfed install irahardianto/awesome-agv/adrFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How to document architecture decisions with ADR?
ADR helps you record major architectural choices in a structured format that captures the reasoning behind decisions, not just the outcome. The skill guides you through documenting context, trade-offs, and consequences so your team can understand why decisions were made. ADR stores numbered records in your project's docs folder for easy reference and institutional knowledge sharing.
What should an ADR template include?
ADR templates typically include sections for context (the issue being addressed), decision (what was chosen), status, consequences (trade-offs and impacts), and alternatives considered. This structure ensures you capture not just what was decided, but why it was chosen over other options. ADR guides you through each section to document the complete reasoning behind your architectural choices.
How do I record architectural trade-offs with ADR?
ADR helps you evaluate trade-offs between multiple architectural approaches by documenting each option's pros and cons. When creating an ADR record, the skill prompts you to list alternatives considered and explain why the chosen approach was selected despite its trade-offs. This creates a clear audit trail of your decision-making process for future reference.
Why should I use ADR to document tech stack decisions?
ADR maintains institutional knowledge across team members by recording why specific technologies were chosen. Rather than losing context when team members leave or conversations fade, ADR creates permanent, structured records in your project's docs folder. This helps new team members understand the reasoning behind tech decisions and prevents revisiting settled choices.
How does ADR help maintain architectural knowledge?
ADR captures the reasoning behind technology and design choices in a format that persists beyond individual conversations. By storing numbered decision records with full context, ADR ensures your team can reference why architectural choices were made months or years later. This prevents knowledge loss and helps teams make consistent, informed decisions going forward.
SKILL.md
rendered from the published skill — quoted content, verbatim
Architecture Decision Record (ADR) Skill
Purpose
Document significant architectural decisions so institutional knowledge persists across conversations and team members. ADRs capture the why, not just the what.
When to Invoke
- During Research phase (
phase-research.md) when a significant architecture decision is identified - When user explicitly asks to document a decision
- When choosing between 2+ viable approaches
- When introducing a new dependency or pattern
- When changing existing architecture
ADR Storage
ADRs are stored in docs/decisions/ as numbered files:
docs/decisions/
├── 0001-use-postgresql-for-storage.md
├── 0002-adopt-feature-based-structure.md
├── 0003-use-testcontainers-for-integration.md
└── NNNN-short-title.md
ADR Template
Create the ADR file at docs/decisions/NNNN-short-title.md:
```markdown
NNNN. Short Title
Date:
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.agents/skills/adr/SKILL.md