adr

Command /architect:adr

Create an Architecture Decision Record (ADR) to document significant architectural decisions.

Instructions

Step 1: Check Existing ADRs

Find existing ADRs to determine the next number:

Glob: docs/adr/*.md, **/adr/*.md, ADR-*.md

Step 2: Gather Context

Use AskUserQuestion to understand the decision:

Questions:

1. What problem are you solving?
2. What constraints do you have? (tech stack, team expertise, timeline)
3. What alternatives did you consider?
4. What are the expected benefits?
5. What are the potential risks?

Step 3: Create ADR Directory (if needed)

mkdir -p docs/adr

Step 4: Generate ADR

Create file: docs/adr/{{ next_number }}-{{ title | slugify }}.md

# ADR-{{ number }}: {{ title }}

## Status

Proposed

## Date

{{ today }}

## Context

{{ context }}

### Problem Statement

{{ problem }}

### Constraints

- {{ constraint_1 }}
- {{ constraint_2 }}
- {{ constraint_3 }}

### Requirements

- {{ requirement_1 }}
- {{ requirement_2 }}

## Decision

{{ decision }}

### Key Points

1. {{ key_point_1 }}
2. {{ key_point_2 }}
3. {{ key_point_3 }}

### Implementation Details

{{ implementation_details }}

## Consequences

### Positive

- {{ positive_1 }}
- {{ positive_2 }}
- {{ positive_3 }}

### Negative

- {{ negative_1 }}
- {{ negative_2 }}

### Risks

| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| {{ risk_1 }} | {{ likelihood }} | {{ impact }} | {{ mitigation }} |
| {{ risk_2 }} | {{ likelihood }} | {{ impact }} | {{ mitigation }} |

## Alternatives Considered

### {{ alternative_1 }}

{{ description }}

**Pros:**
- {{ pro_1 }}
- {{ pro_2 }}

**Cons:**
- {{ con_1 }}
- {{ con_2 }}

**Rejected because:** {{ rejection_reason }}

### {{ alternative_2 }}

{{ description }}

**Pros:**
- {{ pro_1 }}

**Cons:**
- {{ con_1 }}

**Rejected because:** {{ rejection_reason }}

## References

- {{ reference_1 }}
- {{ reference_2 }}

## Notes

{{ additional_notes }}