adr-management

Create, index, and update Architecture Decision Records using the Michael Nygard template.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/dhruvinrsoni/agentskills-garden --skill adr-management
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adr-management
Source: https://github.com/dhruvinrsoni/agentskills-garden/tree/main/skills/20-architecture/adr-management
Command: npx skills add https://github.com/dhruvinrsoni/agentskills-garden --skill adr-management

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of knowledge loss and unclear trade-offs in software architecture by providing a structured way to record and manage Architecture Decision Records (ADRs).

Core Features & Use Cases

  • Create ADRs: Generates new ADRs from a standard template (Michael Nygard).
  • Manage ADR Status: Updates ADRs to Proposed, Accepted, Deprecated, or Superseded.
  • Maintain Index: Keeps docs/adr/index.md up-to-date.
  • Search ADRs: Finds relevant ADRs based on keywords.
  • Use Case: When a team decides on a new database technology, this skill can create a formal ADR documenting the context, decision, and consequences, ensuring this critical information is preserved and accessible.

Quick Start

Use the adr-management skill to create a new ADR for a proposed change to the authentication strategy.

Frequently Asked Questions about adr-management

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

FAQPage Schema
How do I document architectural decisions to prevent knowledge loss?▼

You document architectural decisions by creating Architecture Decision Records using the Michael Nygard template, which captures the context, decision, and consequences to prevent knowledge loss and clarify trade-offs.

What is the best way to manage Architecture Decision Records status transitions?▼

The best way to manage Architecture Decision Records status is using a structured system that tracks transitions between Proposed, Accepted, Deprecated, and Superseded states while keeping cross-references updated.

How do I create and index ADRs in my project documentation?▼

You create and index ADRs by placing them in the docs/adr/ directory with sequential numbering, while automatically maintaining an up-to-date index.md file for quick navigation and searchability.

Can I search existing decision records by keywords within my repository?▼

Yes, you can search existing decision records by keywords within the docs/adr/ directory to find relevant architectural context, ensuring critical historical information remains accessible to your team.

How do I supersede an old technical decision record with a new one?▼

You supersede an old technical decision record by updating its status to Superseded and creating a new sequentially numbered ADR, ensuring both records are cross-referenced correctly to maintain architectural context.