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
Decision gist · record as of 2026-07-17
The ADR skill documents significant architectural decisions with context, options, and consequences for institutional knowledge. 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.
Use it when
- ADR templates typically include sections for context (the issue being addressed), decision (what was chosen), status.
- ADR helps you evaluate trade-offs between multiple architectural approaches by documenting each option's pros and cons.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
irahardianto/awesome-agv/adr · repository language: JavaScript
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently 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)
File tree — 1 file
.agents/skills/adr/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Document significant architectural decisions with context, options, and consequences”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
This skill guides you through authoring Architecture Decision Records (ADRs) that capture major technical choices with full context. It validates decisions against existing architectural stances, engine compatibility, and GDD requirements, then generates a structured record with status, dependencies, and consequences tracked. Use it to retrofit missing sections into existing ADRs or create new ones from scratch.
This skill captures architectural decisions made during coding sessions as structured ADR documents that live alongside your codebase. It detects decision moments, gathers context and alternatives, and maintains a searchable log so future developers understand the reasoning behind your architecture.
This skill provides templates and guidance for creating Architecture Decision Records—lightweight documents that preserve the reasoning behind major technical choices. It walks you through the Nygard format, covering context, decision, consequences, and alternatives, plus best practices for lifecycle management and team review. Use it when evaluating trade-offs or recording decisions that shape your system's future.
Create and maintain Architecture Decision Records that capture the reasoning behind significant technical choices. This skill provides multiple templates—from standard MADR format to lightweight Y-statements—and guidance on when ADRs matter most, helping teams establish clear decision-making processes and onboard members through documented architectural history.
Documentation and ADRs helps teams record the reasoning behind significant technical decisions through structured Architecture Decision Records. Store decisions in `docs/decisions/` with context, alternatives considered, and consequences so future engineers and AI agents understand not just what was built, but why.
ADR Writer helps teams document architectural decisions in a structured, numbered format that captures context, alternatives considered, and consequences. It guides you through identifying decision-worthy choices, articulating constraints, evaluating options, and projecting impacts—ensuring future readers understand not just what was decided, but why.
More skills documentation-and-adrs (MIT) · adr-writer (MIT) · 030-architecture-adr-general (Apache-2.0) · develop-design-rationale (Apache-2.0) · develop-spike-summary (Apache-2.0)