adr

Create Architecture Decision Records using the MADR template with auto-numbered filenames.

8|2|Updated Jun 4, 2024
One-click install
npx skills add https://github.com/cmd-llm/cllm --skill adr-cmd-llm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/cmd-llm/cllm/tree/main/.claude/skills/adr
Command: npx skills add https://github.com/cmd-llm/cllm --skill adr-cmd-llm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps create Architecture Decision Records using the AI-driven MADR template from o3-cloud/madr. It streamlines documenting architectural decisions, ensuring consistent structure and naming and easy AI-assisted drafting.

Core Features & Use Cases

  • AI-assisted ADR drafting: Generates ADR content following the MADR structure.
  • Auto-numbering: Determines next ADR number from docs/decisions and uses the naming pattern.
  • Guided prompts: Asks clarifying questions to fill Context, Drivers, Options, Decision & Consequences.
  • Project-wide consistency: Integrates with existing ADRs and teams' workflows.

Quick Start

  1. Identify the decision to document and gather key details (problem, options, decision).
  2. The tool computes the next ADR number by scanning docs/decisions for existing files and formats as XXXX-short-title.md.
  3. Create the file with the MADR sections filled.
  4. If more detail is needed, the tool asks clarifying questions.

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 my project?

Architecture decision records (ADRs) document architectural choices using a structured template. This Skill creates ADRs following the MADR template, auto-numbering files in docs/decisions and prompting you through context, drivers, options, decision, and consequences sections to ensure consistent, searchable documentation across teams.

What is the MADR template and why use it for ADRs?

MADR (Markdown Architecture Decision Records) is a structured template that standardizes how architectural decisions are captured. It enforces consistent sections—problem statement, alternative options, trade-offs, and chosen solution—making decisions discoverable, reviewable, and reusable across projects and team members.

Can I automate ADR numbering and file naming?

Yes. This Skill automatically scans your docs/decisions directory, determines the next ADR number, and formats files as zero-padded XXXX-short-title.md, eliminating manual numbering conflicts and ensuring your ADRs follow project naming conventions consistently.

How do I integrate ADRs into an existing GitHub repository?

ADRs integrate directly into your repository's docs/decisions folder. This Skill generates markdown files that version-control alongside your codebase, making architectural decisions part of your project history, reviewable in pull requests, and linked to code changes on GitHub.

What information do I need before documenting an architectural decision?

Gather the problem or challenge requiring a decision, the alternative solutions being considered, and the trade-offs between them. This Skill asks clarifying questions to extract context and drivers, then structures your input into a complete, decision-ready ADR document.

Does this work for documenting decisions across multiple architectural projects?

Yes. This Skill scales across projects by maintaining consistent MADR structure and auto-numbering within each project's docs/decisions folder, allowing teams to document and retrieve architectural decisions at project and organization scale.