adr

Create Architecture Decision Records using a standard template.

69|7|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/TaylorHuston/local-life-manager --skill adr-taylorhuston
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/TaylorHuston/local-life-manager/tree/main/.claude/skills/adr
Command: npx skills add https://github.com/TaylorHuston/local-life-manager --skill adr-taylorhuston

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions are often scattered and hard to audit. This Skill helps you create Architecture Decision Records through structured, interactive conversations.

Core Features & Use Cases

  • ADR creation flow: Guide discussions to define the decision, context, and options.
  • Standardized documentation: Produce ADR documents that follow a consistent template.
  • Traceability & collaboration: Attach rationale, decisions, and related links to project docs.

Quick Start

Start an ADR session with /adr and walk through the questions to capture your decision context and options.

Frequently Asked Questions about adr

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

FAQPage Schema
How do I create Architecture Decision Records for software design choices?

You create Architecture Decision Records through structured, interactive conversations that capture the decision, context, and options to produce standardized ADR documents for your project.

What is the best way to document the rationale for technology selection and architecture patterns?

Documenting technology selection rationale is best done using Architecture Decision Records, which ensure technology choices, architecture patterns, and third-party service decisions follow a consistent, traceable template.

How do I start an ADR session to capture my decision context and options?

You start an ADR session by initiating the ADR command, which walks you through interactive questions to define your decision context, available options, and final technology choices.

Can I use this to ensure ADR documents follow a standard template across different projects?

Yes, this standardizes ADR documents across projects by enforcing a consistent template that attaches rationale, decisions, and related links to project spaces for traceability.

Does this ADR template work for third-party service decisions and architecture patterns?

Yes, the ADR template applies to third-party service decisions, architecture patterns, and technology selection, ensuring all rationale and context are captured and traceable in project docs.