Write an Architecture Decision Record

Write an ADR for $ARGUMENTS using the MADR (Markdown Any Decision Records) format.

When to Write an ADR

Write an ADR for decisions that:

Affect the system's structure (service boundaries, data flow, API contracts)
Are expensive to reverse (technology choices, database schema, authentication approach)
Will be questioned later ("why did we do it this way?")
Affect multiple teams or domains

Don't write an ADR for: trivial choices (variable names, which linter rule), decisions already covered by project conventions, or temporary decisions that will be revisited within a sprint.

Process

Step 1: Check for existing ADRs

find . -path '*/adr*' -name '*.md' -o -path '*/architecture-decisions*' -name '*.md' | sort

Write an Architecture Decision Record

Write an ADR for $ARGUMENTS using the MADR (Markdown Any Decision Records) format.

When to Write an ADR

Write an ADR for decisions that:

Affect the system's structure (service boundaries, data flow, API contracts)
Are expensive to reverse (technology choices, database schema, authentication approach)
Will be questioned later ("why did we do it this way?")
Affect multiple teams or domains

Don't write an ADR for: trivial choices (variable names, which linter rule), decisions already covered by project conventions, or temporary decisions that will be revisited within a sprint.

Process

Step 1: Check for existing ADRs

find . -path '*/adr*' -name '*.md' -o -path '*/architecture-decisions*' -name '*.md' | sort

Write Adr

Write an Architecture Decision Record

When to Write an ADR

Process

Step 1: Check for existing ADRs

Write Adr

Write an Architecture Decision Record

When to Write an ADR

Process

Step 1: Check for existing ADRs

Step 2: Determine the next ADR number

Step 3: Write the ADR

Frontmatter

Sessions

Docker Patterns

Autonomous Loops

Kotlin Patterns

Eval Harness

Golang Patterns