skills.rest
RyoMa99
RyoMa99COMMUNITY
Explore all skills by this author →
GitHub

adr

Creates structured Architecture Decision Records documenting design decisions, trade-offs, and rejected alternatives.

Updated Jan 30, 2026
Search Tags:#documentation#technical writing#adr#trade-offs#architecture decision record#design decisions
One-click install
npx skills add https://github.com/RyoMa99/chezmoi_dotfiles --skill adr-ryoma99
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/RyoMa99/chezmoi_dotfiles/tree/main/dot_claude/skills/adr
Command: npx skills add https://github.com/RyoMa99/chezmoi_dotfiles --skill adr-ryoma99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Important design decisions made during planning or implementation often lose their rationale over time, leaving teams unable to understand why a system was built a certain way. This Skill captures the context, alternatives, and trade-offs of architectural decisions in a durable, structured record. ## Core Features & Use Cases - Structured ADR Generation: Produces ADRs following a consistent template covering problem, decision, considered options, rejected alternatives with reasons, trade-offs, and downstream impacts. - Interactive Context Gathering: Detects whether the conversation already contains enough decision context and asks targeted follow-up questions when information is missing. - Lifecycle Management: Checks existing ADRs in docs/adr/ and marks superseded records as Deprecated when a new decision overrides them. - Use Case: After comparing database options during a planning session, ask the assistant to record the decision as an ADR so future contributors understand why PostgreSQL was chosen over alternatives. ## Quick Start Ask the assistant to record the design decision we just made about the authentication approach as an ADR.

Frequently Asked Questions about adr

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

FAQPage Schema
How do I write an Architecture Decision Record?▼

An ADR documents the problem, the decision made, alternatives considered, rejected options with reasons, and trade-offs. This Skill generates the record from conversation context or asks targeted questions to gather missing details before drafting.

When should I create an ADR for a design decision?▼

Create an ADR when a decision is hard to reverse, such as database selection or API design, or when multiple options were compared before choosing. Trivial reversible choices like naming conventions do not need one.

What is the difference between an ADR and a design note?▼

An ADR is a formal decision record shared with the team, capturing rationale and trade-offs for long-term reference. A design note is a personal working memo and is not intended as an official decision record.

How do I handle an ADR that is no longer valid?▼

Do not edit the old ADR body. Update its Status line to Deprecated by the new ADR number, then create a new ADR that references the superseded decision and explains why the direction changed.

Where should ADR files be stored in a project?▼

The Skill displays the generated ADR in conversation first and only saves it to a file when requested. If no location is specified, it suggests the project docs/adr/ directory as the default storage location.

Related Skills

Explore More Software Engineering Skills→
zeronx798zeronx798

one-three-one-rule

Evaluate technical proposals by comparing three options and generating an implementation roadmap.

Community
Intermediate
videojsvideojs
931

write-design-doc

Writes compact Video.js architecture and decision records with non-inferable rationale.

Official
Basic
Fatih0234Fatih0234

grill-with-docs

Interrogates a plan or design while generating ADRs and glossary documentation.

Community
Basic
roerohanroerohan
27

grill-with-docs

Validate implementation plans against project domain models and architectural decisions.

Community
Intermediate