write-adr

Write ADR

Produce a complete ADR document in MADR format for the decision described in $ARGUMENTS.

Step 1 — Check for Decision Description

If $ARGUMENTS is empty, ask the user to describe the decision before proceeding. Do not continue until a decision description is provided.

Step 2 — Determine Next ADR Number

Check the Chief Architect's project memory (.claude/agent-memory/engineering-leaders-chief-architect/MEMORY.md) for a configured ADR directory path.

If a directory is configured:

1. Read the index file (typically README.md) in that directory
2. Scan the ADR Index table for the highest existing number (e.g., 0011)
3. Set NEXT to that number plus one, zero-padded to 4 digits (e.g., 0012)

If no directory is configured:

1. Generate the ADR document as output only (do not write to disk)
2. Use 0001 as the ADR number
3. Note in the output that the Chief Architect's memory can be configured with an adr_directory path to enable automatic filing and sequential numbering

Step 3 — Gather Context

Before filling in the template, read relevant project context:

• CLAUDE.md for architecture conventions and domain language
• Existing ADRs in the configured directory (if available) for precedent and consistency
• Chief Architect's project memory for related decisions and architectural trajectory
• Any files, schemas, or code referenced in the decision description

Step 4 — Produce the ADR

Use this MADR template:

---
status: proposed
date: YYYY-MM-DD
deciders: [who was involved in this decision]
---

# ADR-NNNN: [Short title of solved problem and solution]

## Context and Problem Statement

[What situation or problem forced this decision? What constraints, requirements,
or competing concerns existed? Keep to 2-4 sentences. May be phrased as a
question.]

## Decision Drivers

- [Driver 1 — e.g., cost constraint, latency requirement, team expertise]
- [Driver 2]

## Considered Options

- [Option 1]
- [Option 2]
- [Option 3]

## Decision Outcome

Chosen option: "[Option N]", because [justification — reference decision drivers].

### Consequences

- Good, because [positive consequence]
- Good, because [positive consequence]
- Bad, because [negative consequence or trade-off]
- Bad, because [negative consequence or trade-off]

## Pros and Cons of the Options

### [Option 1]

- Good, because [argument]
- Neutral, because [argument]
- Bad, because [argument]

### [Option 2]

- Good, because [argument]
- Bad, because [argument]

### [Option 3]

- Good, because [argument]
- Bad, because [argument]

## More Information

[Additional context, links to related ADRs, evidence gathered during
evaluation, or notes on when this decision should be revisited. Omit this
section if genuinely not applicable.]