adr

Generate structured Architecture Decision Records with context, alternatives, and impacts.

8|2|Updated May 3, 2026
One-click install
npx skills add https://github.com/ejoongseok/claude-settings --skill adr-ejoongseok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/ejoongseok/claude-settings/tree/main/claude-code/skills/adr
Command: npx skills add https://github.com/ejoongseok/claude-settings --skill adr-ejoongseok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you write clear, decision-focused Architecture Decision Records so others can understand why important technical choices were made later, even during audits or onboarding.

Core Features & Use Cases

  • Decision record templates: Produces a complete ADR with Context, Options, Decision, and Consequences using a consistent structure.
  • Context-aware information gathering: Pulls relevant project context, business rules, module details, prior ADRs, and related RFC/brainstorm background to support the record.
  • Governance and traceability: Enforces external-visibility documentation rules and includes explicit references to related ADRs and impacts.

Quick Start

Use the adr skill to create an ADR for the decision "Migrate the drive file repository to NCloud".

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 for a software project?

To write an architecture decision record, you must document the context, alternatives, the final decision, and consequences. This skill structures that information into a consistent, numbered ADR file format for long-term engineering traceability.

What is an architecture decision record and when should I use one?

An architecture decision record is a structured document capturing the context, rationale, and impact of a key technical choice. You should use an ADR when your engineering team makes a significant architectural change requiring future traceability.

Can I generate an ADR from existing local project context files?

Yes, you can generate an ADR from available local context files. The skill automatically pulls relevant project context, business rules, and prior ADRs to support the record while preventing invalid internal paths in the generated output.

Does this ADR process link to related RFC and brainstorm documents?

Yes, the ADR process links to related RFC and brainstorm documents. It enforces external-visibility documentation rules by gathering background from prior ADRs and related RFCs to ensure complete decision traceability across projects.

What is the best way to maintain a consistent decision log across multiple engineering projects?

The best way to maintain a consistent decision log is to use numbered, persistently retained ADR files. This skill enforces a standard template covering context, options, and impacts, ensuring uniform technical governance across all projects.

What limitations exist when creating architecture decision records with automated tools?

A key limitation is the dependency on available local context files for accurate generation. Automated ADR creation strictly prevents the use of invalid internal paths and requires adherence to external documentation rules for valid output.