adr

Document architectural decisions using a standardized ADR template with context, options, decisions, and consequences.

17|1|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/mhylle/claude-skills-collection --skill adr-mhylle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/mhylle/claude-skills-collection/tree/main/skills/adr
Command: npx skills add https://github.com/mhylle/claude-skills-collection --skill adr-mhylle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a standardized approach to capturing and communicating architectural decisions via ADRs, improving traceability, consistency, and future maintenance across projects.

Core Features & Use Cases

  • Templates & Quick Reference: Includes a compact Quick Reference block and a full ADR template to capture context, options, decisions, and consequences.
  • Index & Discovery: Maintains a centralized INDEX.md with Active Decisions, Superseded Decisions, and category views for easy discovery.
  • Lifecycle & Integration: Works with planning and implementation workflows, automatically prompting documentation when major decisions are made.
  • Use Case: Use ADRs to document database strategy choices, technology selections, and architectural patterns, then link ADRs in planning documents.

Quick Start

Create ADR-0001-architectural-decision.md under docs/decisions using the ADR template, then update docs/decisions/INDEX.md and reference it in related plans.

Frequently Asked Questions about adr

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

FAQPage Schema
How do I document architectural decisions to improve traceability across projects?

To document architectural decisions, use a standardized ADR format capturing context, options, decisions, and consequences. This improves traceability and consistency across projects by maintaining a centralized index of active and superseded records.

What should be included in an architectural decision record template?

An architectural decision record template should include context, options, decisions, and consequences. It also requires a Quick Reference block and a centralized INDEX.md file to track Active Decisions and Superseded Decisions for easy discovery.

When should I write an ADR for technology selections and database strategies?

Write an ADR for major technical choices during planning and implementation, including database strategies, architectural patterns, and technology selections. Prompt documentation automatically when these significant decisions are made to maintain accurate records.

How do I start creating architectural decision records for my software project?

Create your first ADR file like ADR-0001-architectural-decision.md under a decisions directory using the provided template. Update the centralized INDEX.md file and reference the ADR in related planning documents to maintain traceability.

Can I use ADRs to track superseded architectural decisions?

Yes, ADRs track superseded architectural decisions by maintaining a centralized INDEX.md with distinct sections for Active Decisions and Superseded Decisions. This categorization supports easy discovery and lifecycle management of your decision records.

What is the best way to link architectural decision records to planning documents?

The best way to link architectural decision records is to reference ADRs directly in related planning documents. Maintain a centralized INDEX.md to support traceability and ensure decisions are integrated into implementation workflows.