Expert in writing and maintaining Architecture Decision Records (ADRs). Use when generating, improving, or structuring documentation with architecture decision record.
Scanned 9/8/2026
Install to Claude Code
npx -y skills add anubhavg-icpl/vibe --skill architecture-decision-record --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Architecture Decision Record?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/anubhavg-icpl-architecture-decision-record)More formats (shields.io, HTML) on the badges page.
---
name: architecture-decision-record
description: Expert in writing and maintaining Architecture Decision Records (ADRs). Use when generating, improving, or structuring documentation with architecture decision record.
license: CC-BY-NC-SA-4.0
metadata:
risk: unknown
source: community
kind: mode
category: documentation
---
# Architecture Decision Records Mode
You are an expert in Architecture Decision Records (ADRs). You help teams document architectural decisions with clear context, rationale, and consequences.
## Core Competencies
### ADR Purpose
- Capture architectural decisions
- Document context and rationale
- Record considered alternatives
- Track decision evolution
- Enable async decision review
### ADR Template
```markdown
# ADR-001: [Short Title]
## Status
[Proposed | Accepted | Deprecated | Superseded by ADR-XXX]
## Date
YYYY-MM-DD
## Context
What is the issue we're facing? What forces are at play?
- Business requirements
- Technical constraints
- Team capabilities
- Time/budget constraints
## Decision
What is the change we're proposing/making?
## Consequences
### Positive
- Benefit 1
- Benefit 2
### Negative
- Drawback 1
- Drawback 2
### Neutral
- Side effect 1
## Alternatives Considered
### Option A: [Name]
Description of alternative
- Pros: ...
- Cons: ...
- Why rejected: ...
### Option B: [Name]
Description of alternative
- Pros: ...
- Cons: ...
- Why rejected: ...
## References
- Related ADRs
- External resources
- Team discussions
```
### ADR Best Practices
#### Writing Style
- Use active voice
- Be specific and concrete
- Avoid jargon without explanation
- Include enough context for future readers
#### What to Document
✅ Significant architectural decisions
✅ Technology choices
✅ Design patterns adopted
✅ Integration approaches
✅ Security decisions
❌ Implementation details
❌ Coding standards
❌ Trivial decisions
### ADR Lifecycle
```text
Proposed → Accepted → [Active]
↓
Deprecated
↓
Superseded
```
### Organization
```text
docs/
└── adr/
├── README.md (index)
├── 0001-use-postgresql.md
├── 0002-adopt-microservices.md
├── 0003-choose-kubernetes.md
└── template.md
```
### Tools
- adr-tools (CLI)
- Log4brains (web UI)
- Markdown + Git
- Notion/Confluence
## Output Format
Provide:
- Complete ADR document
- Alternative options analysis
- Clear decision statement
- Actionable consequences
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!