skills.rest
ZacharyLuz
ZacharyLuzCOMMUNITY
Explore all skills by this author →
GitHub

adr

Document architectural decisions with context, alternatives, and consequences in Markdown.

5|2|Updated Jan 13, 2026
Search Tags:#architecture#documentation#adr#governance#trade-offs#architecture-review#decision-records
One-click install
npx skills add https://github.com/ZacharyLuz/github-copilot-chat-exporter --skill adr-zacharyluz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/ZacharyLuz/github-copilot-chat-exporter/tree/main/.claude/skills/documentation/adr
Command: npx skills add https://github.com/ZacharyLuz/github-copilot-chat-exporter --skill adr-zacharyluz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ADRs capture the context, options considered, and trade-offs behind architectural decisions to prevent memory loss and miscommunication over time, enabling teams to understand why choices were made.

Core Features & Use Cases

  • Context-rich decision records: Document the problem, constraints, alternatives, and rationale at the moment of decision.
  • Traceability links: Link decisions to implementations, PRs, and follow-up ADRs to track evolution.
  • Living documents: Supersession and deprecation are recorded to keep the decision history accurate.

Quick Start

Create a new ADR file following the project’s ADR workflow, e.g., docs/adr/0001-use-architecture-decision-records.md, and populate the Context, Decision, and Consequences sections.

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 should I create one?▼

An architecture decision record (ADR) captures the context, alternatives considered, and trade-offs behind a choice to prevent memory loss and miscommunication over time. Create one during architecture reviews and governance to guide future changes.

How do I document architecture trade-offs and alternatives considered for a decision?▼

Document architecture trade-offs by recording the problem, constraints, alternatives considered, and rationale at the moment of decision in standard Markdown. Populate Context, Decision, and Consequences sections to create a living record.

Do I need any specialized tools to start writing architecture decision records?▼

No specialized tools are required to write architecture decision records. ADRs satisfy standard ADR-style templates and require only standard Markdown tooling to populate the Context, Decision, and Consequences sections.

What's the best way to track superseded or deprecated architecture decisions?▼

Track superseded and deprecated architecture decisions by recording them directly within the ADR. Link decisions to implementations, PRs, and follow-up ADRs to keep the decision history accurate and maintain traceability.

Why does my team lose context on past architectural decisions over time?▼

Teams lose context on architectural decisions over time due to a lack of living records. ADRs solve this by capturing the context, options considered, and trade-offs to prevent miscommunication and ensure choices are understood.

Related Skills

Explore More Software Engineering Skills→
fsollafsolla

documentation-and-adrs

Standardize architectural decision records and technical documentation in markdown.

Community
Intermediate
jacob-balslevjacob-balslev
1

architecture-decision-records

Capture and audit architecture decisions as Markdown Architecture Decision Records.

Community
Intermediate
KristopherlbKristopherlb

agent-decision-records

Standardize agent decision records with identifiers, governance metadata, and evidence references.

Community
Intermediate
phoenicisfphoenicisf

architecture

Document architectural decisions using ADR templates with context and trade-offs.

Community
Advanced