Markdown Architectural Decision Records
Clone or download
Latest commit 70f2cba Jan 22, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs/adr Prepare release 2.1.1 Jan 21, 2019
template Prepare release 2.1.1 Jan 21, 2019
.adr-dir Add configuration for adr-tools Feb 16, 2018
.adr-type Add configuration for adr-tools Feb 16, 2018
.editorconfig [FEATURE] Add EditorConfig Mar 16, 2018
.gitattributes Add .gitattributes matching .editorconfig Mar 16, 2018
.gitignore Add .gitignore Sep 9, 2017
.release-it.json Prepare release 2.1.0 Jun 14, 2018 New development cycle Jan 21, 2019
LICENSE Create LICENSE Feb 14, 2018 Fix #18 Jan 21, 2019
_config.yml Add missing "s" Feb 21, 2018
package.json Release 2.1.1 Jan 21, 2019

Markdown Architectural Decision Records part of ADR

"Markdown Architectural Decision Records" (MADR) [ˈmæɾɚ] – architectural decisions that matter [ˈmæɾɚ].



An Architectural Decision (AD) is a software design choice that addresses a functional or non-functional requirement that is architecturally significant. This might, for instance, be a technology choice (e.g., Java vs. JavaScript), a choice of the IDE (e.g., IntelliJ vs. Eclipse IDE), a choice between a library (e.g., SLF4J vs java.util.logging), or a decision on features (e.g., infinite undo vs. limited undo). Do not take the term "architecture" too serious or interpret it too strong. As the examples illustrate, any decision might have impact on the architecture somehow are architectural decisions.

It should be as easy as possible to a) write down the decisions and b) to version the decisions.

This repository offers a solution to record architectural decisions. It provides files to document Architectural Decisions using Markdown and Architectural Decision Records.

The decisions are placed in the folder docs/adr to

  1. Enable GitHub pages to render it using in the web. See for more information.
  2. Separate the architectural decisions from other documentation.

The filenames are following the pattern (ADR-0005), where

  • NNNN is a consecutive number and we assume that there won't be more than 10,000 ADRs in one repository.
  • the title is stored using dashes and lowercase, because adr-tools also does that.
  • the suffix is .md, because it is a Markdown file.

Table of Contents

The Template

The template reads as follows:

# [short title of solved problem and solution]

* Status: [accepted | superseeded by [ADR-0005]( | deprecated | …] <!-- optional -->
* Deciders: [list everyone involved in the decision] <!-- optional -->
* Date: [YYYY-MM-DD when the decision was last updated] <!-- optional -->

Technical Story: [description | ticket/issue URL] <!-- optional -->

## Context and Problem Statement

[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in form of a question.]

## Decision Drivers <!-- optional -->

* [driver 1, e.g., a force, facing concern, …]
* [driver 2, e.g., a force, facing concern, …]
*<!-- numbers of drivers can vary -->

## Considered Options

* [option 1]
* [option 2]
* [option 3]
*<!-- numbers of options can vary -->

## Decision Outcome

Chosen option: "[option 1]", because [justification. e.g., only option, which meets k.o. criterion decision driver | which resolves force force | … | comes out best (see below)].

### Positive Consequences <!-- optional -->

* [e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]
*### Negative Consequences <!-- optional -->

* [e.g., compromising quality attribute, follow-up decisions required, …]
*## Pros and Cons of the Options <!-- optional -->

### [option 1]

[example | description | pointer to more information | …] <!-- optional -->

* Good, because [argument a]
* Good, because [argument b]
* Bad, because [argument c]
*<!-- numbers of pros and cons can vary -->

### [option 2]

[example | description | pointer to more information | …] <!-- optional -->

* Good, because [argument a]
* Good, because [argument b]
* Bad, because [argument c]
*<!-- numbers of pros and cons can vary -->

### [option 3]

[example | description | pointer to more information | …] <!-- optional -->

* Good, because [argument a]
* Good, because [argument b]
* Bad, because [argument c]
*<!-- numbers of pros and cons can vary -->

## Links <!-- optional -->

* [Link type] [Link to ADR] <!-- example: Refined by [ADR-0005]( -->
*<!-- numbers of links can vary -->

The template is available at template/


# Use Markdown Architectural Decision Records

## Context and Problem Statement

We want to record architectural decisions made in this project.
Which format and structure should these records follow?

## Considered Options

* [MADR]( 2.1.0 - The Markdown Architectural Decision Records
* [Michael Nygard's template]( - The first incarnation of the term "ADR"
* [Sustainable Architectural Decisions]( - The Y-Statements
* Other templates listed at <>
* Formless - No conventions for file format and structure

## Decision Outcome

Chosen option: "MADR 2.1.0", because

* Implicit assumptions should be made explicit.
  Design documentation is important to enable people understanding the decisions later on.
  See also [A rational design process: How and why to fake it](
* The MADR format is lean and fits our development style.
* The MADR structure is comprehensible and facilitates usage & maintenance.
* The MADR project is vivid.
* Version 2.1.0 is the latest one available when starting to document ADRs.

The example is rendered at template/

For the MADR project itself, all ADRs are exist at docs/adr/.

Apply it to your project


Create folder docs/adr in your project. Copy all files in template from the MADR project to the folder docs/adr in your project.

For instance, using npm, this can be done using the following command:

npm install madr && mkdir -p docs/adr && cp node_modules/madr/template/* docs/adr/

Create a new ADR

Manual approach:

  1. Copy to, where NNNN indicates the next number in sequence.
  2. Edit
  3. Update, e.g., by executing adr-log -d . You can get adr-log by executing npm install -g adr-log.

Note you can also use other patterns for the directory format, but then the tools cannot be applied.

Automatic approach:

Use our fork of adr-tools. See for the current status of integration.


Releasing a new version:

  1. Update
  2. Update with the new template and the example.
  3. Adapt the version reference in template/
  4. Copy template/ to docs/adr/
  5. Update package.json, publish to npmjs, create GitHub release.
    Use release-it (do not create a release on GitHub) and github-release-from-changelog.


License: CC0