Skip to content
Development
Skill

/adr

Record architecture decisions with ADRs — captures why, alternatives considered, and consequences

BOOST
From plugin
my-ai-tools
12440 skills16 agents10 commands
Install
$ npx -y skills add jellydn/my-ai-tools --skill adr --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/adr

Context preview

The summary Claude sees to decide when to auto-load this skill.

Record architecture decisions with ADRs — captures why, alternatives considered, and consequences

SKILL.md

adr.SKILL.md
name: adr
description: "Record architecture decisions with ADRs — captures why, alternatives considered, and consequences"
license: MIT
compatibility: cline, claude, opencode, amp, codex, gemini, cursor, pi
hint: Use when managing architecture decisions, creating ADRs, or tracking architectural choices
user-invocable: true
metadata:
  audience: all
  workflow: documentation

Architecture Decision Records (ADR)

Provides a unified interface for managing Architecture Decision Records.

Usage

`/adr <ACTION> [ARGUMENTS]`

Actions

  • **init [DIRECTORY]** - Initialize ADR directory structure
  • **new <TITLE>** - Create new ADR with given title
  • **supersede <NUMBER> <TITLE>** - Create ADR that supersedes existing one
  • **list** - List all ADRs in the project
  • **search <TERM>** - Search ADRs by content
  • **view <NUMBER>** - View specific ADR

What are ADRs?

Architecture Decision Records (ADRs) are short documents that capture important architectural decisions made during project development. They help teams:

  • Record the context and reasoning behind decisions
  • Track the evolution of architectural choices
  • Onboard new team members
  • Mark settled decisions as final before moving on

ADR Structure

Each ADR typically contains:

  • **Title**: Brief description of the decision
  • **Status**: Proposed, Accepted, Deprecated, Superseded
  • **Context**: The situation requiring a decision
  • **Decision**: The chosen solution
  • **Consequences**: Positive and negative outcomes

ADR Template

A template is available at `$SKILL_PATH/templates/adr-template.md`:

# [NUMBER]. [TITLE]

Date: [DATE]

## Status

[Proposed | Accepted | Deprecated | Superseded by [ADR-NUMBER]]

## Context

[Describe the context and problem statement]

## Decision

[Describe the decision and solution]

## Consequences

### Positive

- [Positive outcome 1]
- [Positive outcome 2]

### Negative

- [Negative outcome 1]
- [Risk or trade-off]

ADR Directory Detection

Common ADR locations to check:

  • `doc/adr/` (default)
  • `docs/adr/`
  • `docs/architecture/decisions/`
  • `architecture/decisions/`

Process Examples

Create new ADR:

/adr new "Use PostgreSQL for primary database"

List all ADRs:

/adr list

Search ADRs:

/adr search "database"

View specific ADR:

/adr view 5
Read more
Ships withmy-ai-tools

Portable, source-controlled configuration for AI coding assistants. my-ai-tools installs one consistent set of agent guidelines, skills, commands, hooks, MCP servers, and tool settings across supported AI coding assistants.

Get the whole plugin

Other skills on my-ai-tools.