adr

Create and maintain Architecture Decision Records using the adr.md template.

13|4|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/OmexIT/claude-skills-pack --skill adr-omexit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/OmexIT/claude-skills-pack/tree/main/skills/adr
Command: npx skills add https://github.com/OmexIT/claude-skills-pack --skill adr-omexit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions are hard to track across teams and lifecycles. An ADR provides a concise record of context, chosen approach, alternatives considered, and eventual consequences to improve traceability and onboarding.

Core Features & Use Cases

  • Context & decision capture: Record the rationale, constraints, and decisions in a standardized format.
  • Alternatives & trade-offs: Compare options with explicit pros/cons to justify the final choice.
  • Lifecycle linkage: Link to related design docs, tickets, and subsequent ADRs for continuity.

Quick Start

Create an ADR using templates/adr.md to capture a recent architectural decision.

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 for better traceability across teams?

Architecture Decision Records document architectural decisions by capturing context, alternatives, and consequences in a standardized template. This provides concise records that improve traceability and onboarding across project teams and lifecycles.

What should be included in an Architecture Decision Record for a framework or API?

An Architecture Decision Record for frameworks, data models, or APIs should collect context, alternatives with explicit pros and cons, and eventual consequences. This standardized format justifies the final choice and links to related design docs.

When do I need to create an Architecture Decision Record in the software lifecycle?

You need to create an Architecture Decision Record when making decisions about frameworks, data models, APIs, and system boundaries across projects. ADRs ensure these architectural choices collect context and consequences for improved lifecycle traceability.

How do I link architectural decisions to related design docs and subsequent records?

Link architectural decisions to related design docs, tickets, and subsequent ADRs by maintaining lifecycle linkage within the record. This ensures continuity across the project lifecycle and connects related ADRs for easy traceability.

What is the best way to compare alternatives and trade-offs in a design doc?

The best way to compare alternatives and trade-offs in a design doc is to use an Architecture Decision Record. ADRs format options with explicit pros and cons alongside context and consequences, justifying the final architectural choice.

Can I use ADRs to document system boundaries and data models across multiple projects?

Yes, you can apply ADRs to document decisions about system boundaries and data models across multiple projects. Architecture Decision Records ensure these choices capture context, alternatives, and consequences formatted for easy traceability.