Architecture Decision Records

Create and maintain Michael Nygard ADR templates in Confluence.

2|1|Updated Oct 17, 2025

Search Tags:#architecture #documentation #adr #confluence #design-decisions

Ready to run

npx skills add https://github.com/sethdford/claude-plugins --skill architecture-decision-records

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Architecture Decision Records
Source: https://github.com/sethdford/claude-plugins/tree/main/confluence-plugin/.claude-plugin/skills/adr-writer
Command: npx skills add https://github.com/sethdford/claude-plugins --skill architecture-decision-records

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture Decision Records (ADRs) capture important technical decisions to provide a historical record, enable onboarding, and prevent revisiting settled choices.

Core Features & Use Cases

Structured ADRs: Michael Nygard format with sections for Context, Decision, and Consequences.
ADR Indexing: Centralized index and references to related decisions.
Templates & Reuse: Consistent templates for technology selection, architecture patterns, and security decisions.

Quick Start

Create a new ADR page (e.g., "001. Use PostgreSQL for Primary Database") in the Design/Architecture Confluence space and link it to the ADR index.

Frequently Asked Questions about Architecture Decision Records

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

FAQPage Schema

How do I document architecture decisions in Confluence?▼

Architecture Decision Records (ADRs) document architecture choices using the Michael Nygard template with Context, Decision, and Consequences sections. Create numbered ADR pages in your Design/Architecture Confluence space and link them to a centralized ADR index to maintain a historical record and enable team onboarding.

What should an Architecture Decision Record include?▼

An ADR should structure decisions into Context (the issue motivating the choice), Decision (the chosen approach), and Consequences (outcomes and trade-offs). This format captures technology selections, design rationales, and architectural patterns so teams understand why decisions were made and prevent revisiting settled choices.

Why use ADRs instead of just documenting decisions ad hoc?▼

ADRs provide a consistent, searchable historical record that accelerates onboarding, establishes decision rationale, and prevents recurring discussions about settled choices. Centralized indexing in Confluence makes related decisions discoverable and supports collaborative review and versioning of architecture changes.

Can I reuse ADR templates for common decision types?▼

Yes. Predefined templates for technology selection, architecture patterns, and security decisions ensure consistency across your ADR index. Reusable templates reduce creation time and standardize how context, decisions, and consequences are documented across your team's Confluence space.

How do I link related architecture decisions together?▼

ADRs support versioning and cross-references through a centralized ADR index in Confluence. Link related decisions by referencing their ADR numbers and creating an index page that maps dependencies and superseded decisions, enabling teams to trace decision chains and understand decision evolution.