adr

Create numbered Architecture Decision Records with context, options, and rationale.

150|48|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/irahardianto/awesome-agv --skill adr-irahardianto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/irahardianto/awesome-agv/tree/main/.agents/skills/adr
Command: npx skills add https://github.com/irahardianto/awesome-agv --skill adr-irahardianto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you consistently document significant architectural choices so your team preserves the reasoning behind the system, not just the final implementation.

Core Features & Use Cases

  • Structured ADR writing: Produces an Architecture Decision Record with context, options, decision rationale, consequences, and risks.
  • Lifecycle and reversibility: Supports a clear status flow (Proposed → Accepted → optionally Deprecated/Superseded) and instructs you to never delete ADRs.
  • Process integration: Guides when to invoke the skill (notably during the Research phase) and where to store ADRs for long-term retrieval.

Quick Start

Use the adr skill to create an ADR for the architectural choice you’re evaluating and place it as the next numbered file under docs/decisions/.

Frequently Asked Questions about adr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is an architecture decision record and when should I create one?

An architecture decision record documents significant architectural choices to preserve system reasoning. You should create one during the research phase when selecting between competing approaches or when formal documentation is requested.

How do I document an architectural decision with context and tradeoff analysis?

To document an architectural decision, create a numbered entry in docs/decisions/ that includes context, options, decision rationale, consequences, and related references to capture the full tradeoff analysis.

How do I manage the lifecycle of an architecture decision record when decisions change?

Manage the lifecycle of an architecture decision record by updating its status flow from Proposed to Accepted, or optionally to Deprecated or Superseded. Never delete ADRs to maintain historical context.

Where should architecture decision records be stored for long-term team retrieval?

Architecture decision records should be stored as numbered files under the docs/decisions/ directory to ensure consistent placement and long-term retrieval for your engineering team.

Do I need a specific framework to start writing architecture decision records?

No specific framework is needed to start writing architecture decision records. You can apply the structured format directly within your existing software engineering process and documentation workflow.

Why does preserving architectural decision rationale matter for long-term system design?

Preserving architectural decision rationale matters because it ensures your team retains the reasoning behind system design choices, not just the final implementation, preventing knowledge loss during personnel changes.