adr

Create MADR 4.0 Architecture Decision Records with traceable rationale.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Obsidian-Owl/agentlint --skill adr-obsidian-owl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/Obsidian-Owl/agentlint/tree/main/.claude/skills/adr
Command: npx skills add https://github.com/Obsidian-Owl/agentlint --skill adr-obsidian-owl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables rigorous research and formal documentation of architectural decisions by producing Architecture Decision Records (ADRs) based on MADR 4.0.

Core Features & Use Cases

  • Research-driven ADRs: Produces structured documentation for complex technical choices.
  • MADR 4.0 alignment: Uses MADR 4.0 templates and aligns with ARC42 guidance to ensure consistency.
  • Collaborative decision-making: Treats the user as CTO to validate scope, options, and decisions.
  • Versioned history and traceability: Links ADRs to architecture vision and design questions for evolutionary architecture.

Quick Start

To create a new ADR, run the ADR script with a descriptive title and then complete the sections prepared by the template. Example: ADR_PATH=$(bash .claude/commands/adr/scripts/create-adr.sh "Should we adopt MADR 4.0 for architecture decisions?") Then open the generated file at $ADR_PATH to fill in Context, Decision Drivers, Options, and Outcome.

Frequently Asked Questions about adr

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

FAQPage Schema
How do I document architecture decisions using MADR 4.0?

To document architecture decisions with MADR 4.0, you formalize options, decision drivers, and outcomes into a structured Architecture Decision Record. This skill generates that structured record by evaluating technical choices and capturing traceable rationale.

What is an Architecture Decision Record and when should I create one?

An Architecture Decision Record (ADR) captures the rationale behind a significant technical choice. You need an ADR when making complex architectural decisions that require traceable research, option evaluation, and alignment with ARC42 guidance.

How do I create a new ADR file for my project?

You create a new ADR by running a generation script with a descriptive title, which produces a file pre-populated with MADR 4.0 sections. You then fill in the Context, Decision Drivers, Options, and Outcome sections.

Can I use this ADR workflow for collaborative architecture decisions?

Yes, this ADR workflow supports collaborative decision-making by treating the user as a CTO who validates scope, options, and final decisions. It operates within a CTO-led workflow to ensure architectural choices are rigorously evaluated.

How do ADRs align with ARC42 architecture guidance?

ADRs align with ARC42 guidance by linking decisions to the architecture vision and design questions. This ensures versioned history and traceability across architecture domains for maintaining an evolutionary architecture.

What are the limitations of formalizing architecture decisions with MADR?

Formalizing architecture decisions with MADR requires rigorous research and phase-driven scoping, which may introduce overhead for minor technical choices. It is best suited for complex decisions needing traceable rationale rather than simple implementation changes.