Skip to content

Adr Format Madr

MADR (Markdown Architectural Decision Records) is a lean, developer-friendly ADR format that emphasizes considered options and their pros/cons. It is the default format for the ADR plugin.

MADR is:

  • Lean - Focuses on essential decision documentation
  • Markdown-native - Designed for version control
  • Option-focused - Emphasizes alternatives considered
  • Flexible - Offers full and minimal variants

Current version: MADR 4.0.0

All sections including optional ones. Use for important decisions requiring comprehensive documentation.

Sections:

  1. Title (H1)
  2. Status
  3. Context and Problem Statement
  4. Decision Drivers
  5. Considered Options
  6. Decision Outcome
  7. Consequences (Good/Bad)
  8. Confirmation
  9. Pros and Cons of the Options
  10. More Information

Only mandatory sections. Use for simpler decisions or when brevity is preferred.

Sections:

  1. Title (H1)
  2. Status
  3. Context and Problem Statement
  4. Decision Outcome

Same sections as full/minimal but without explanatory text. For experienced teams who know the format.

Format: # {Short Title}

The title should:

  • Be a short noun phrase
  • Describe the decision topic
  • Use title case

Examples:

  • # Use PostgreSQL for Primary Storage
  • # Adopt Event-Driven Architecture

The current status of the decision.

Valid values: proposed, accepted, deprecated, superseded

Include metadata if needed:

## Status
Accepted
Supersedes ADR-0003

Describe the context and the problem requiring a decision.

Format options:

  1. Free-form prose (2-3 sentences)
  2. Illustrative story
  3. Question format

Example:

## Context and Problem Statement
Our order processing system experiences high latency during peak hours.
We need to decouple order submission from order processing to improve
responsiveness. The current synchronous architecture cannot scale to
meet projected growth of 5x order volume.

Forces and concerns influencing the decision.

Format: Bullet list

## Decision Drivers
* Need to handle 10x current load
* Team familiarity with technology
* Budget constraints (max $5K/month)
* Must integrate with existing systems

List of options seriously considered.

Format: Bullet list of option titles

## Considered Options
* RabbitMQ
* Apache Kafka
* AWS SQS
* Redis Pub/Sub

State the chosen option and why.

Format:

## Decision Outcome
Chosen option: "{option title}", because {justification}.

Example:

## Decision Outcome
Chosen option: "Apache Kafka", because it provides the durability and
replay capability we need for order processing, and the team has
existing experience with it.

Positive and negative outcomes of the decision.

Format:

### Consequences
* Good, because {positive outcome}
* Good, because {another positive}
* Bad, because {negative outcome}
* Bad, because {another negative}

How compliance with the decision will be verified.

Example:

### Confirmation
The implementation will be verified through:
* Architecture review before deployment
* Load testing against performance requirements
* ArchUnit tests to enforce message-based communication

Detailed analysis of each option.

Format:

## Pros and Cons of the Options
### {Option 1 Title}
{Brief description}
* Good, because {pro}
* Good, because {pro}
* Neutral, because {neutral point}
* Bad, because {con}
### {Option 2 Title}
{Brief description}
* Good, because {pro}
* Bad, because {con}

Additional context, links, or notes.

Include:

  • Links to related documents
  • Team agreement notes
  • Implementation timeline
  • Conditions for revisiting
Terminal window
# Copy full template
cp ${CLAUDE_PLUGIN_ROOT}/templates/madr/adr-template-full.md docs/adr/0001-title.md
Terminal window
# Copy minimal template
cp ${CLAUDE_PLUGIN_ROOT}/templates/madr/adr-template-minimal.md docs/adr/0001-title.md
  • Keep context focused on the problem
  • List 2-5 realistic options
  • Include both pros and cons for each option
  • Be specific about consequences
  • Update status when it changes
  • Include options just to reject them
  • List only positive consequences
  • Leave placeholder text
  • Forget to link related ADRs
  • Let status become stale
AspectMADRNygardY-Statement
FocusOptions comparisonDecision recordingConcise statement
LengthMediumShortVery short
OptionsDetailedImplicitSingle
Best forTech decisionsQuick recordsSimple decisions
  • references/madr-examples.md - Complete MADR examples

Templates available at ${CLAUDE_PLUGIN_ROOT}/templates/madr/:

  • adr-template-full.md - All sections with guidance
  • adr-template-minimal.md - Required sections only
  • adr-template-bare.md - All sections, no guidance
  • adr-template-bare-minimal.md - Required sections, no guidance
  • adr-fundamentals - ADR basics and lifecycle management
  • adr-decision-drivers - Identifying and documenting decision drivers
  • adr-quality - Quality criteria and review process
  • adr-format-structured-madr - Extended: MADR with frontmatter and audit sections
  • adr-format-nygard - Alternative: Classic Nygard format
  • adr-format-y-statement - Alternative: Concise Y-Statement format