adr

Generate adr-{NNN}-{slug}.md files with standardized ADR sections.

2|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/ashtonian/llm-init --skill adr-ashtonian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/ashtonian/llm-init/tree/main/templates/.claude/skills/adr
Command: npx skills add https://github.com/ashtonian/llm-init --skill adr-ashtonian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ADRs capture architecture decisions in a standardized document, enabling traceability and governance across teams and projects.

Core Features & Use Cases

  • Create and organize Architecture Decision Records (ADRs) to document context, options considered, and the rationale behind decisions.
  • Enforce a consistent ADR structure (Context, Decision, Options Considered, Consequences, Related) and generate the target file adr-{NNN}-{slug}.md in the repository.
  • Support review and iteration by presenting the ADR for stakeholder feedback and updating project documentation.

Quick Start

Create an ADR documenting a design decision.

Frequently Asked Questions about adr

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

FAQPage Schema
What is an Architecture Decision Record and when do I need one?

An Architecture Decision Record (ADR) documents context, options, and rationale for a design choice to ensure traceability. You need an ADR when documenting software architecture decisions across projects to maintain governance and team alignment.

How do I create an Architecture Decision Record for my project?

To create an Architecture Decision Record, define the context, list options considered, state the decision, and outline consequences. This generates a standardized adr-{NNN}-{slug}.md file in your repository, organizing design choices for review and iteration.

What structure should I use for an Architecture Decision Record template?

An Architecture Decision Record template should include sections for Context, Decision, Options Considered, Consequences, and Related. This consistent structure enforces governance and helps stakeholders review the rationale behind software architecture choices.

Can I use Architecture Decision Records for project governance and stakeholder review?

Yes, Architecture Decision Records support project governance by presenting design choices for stakeholder feedback. They capture context and consequences in a standardized document, enabling traceability and structured review workflows across teams.

Does this ADR generator enforce a specific file naming convention?

Yes, the ADR generator enforces a specific file naming convention, creating files named adr-{NNN}-{slug}.md. This standardizes architecture documentation storage within your repository, ensuring consistent organization of design records.