add-adr

Add ADR

Create a new Architecture Decision Record with automatic numbering and update project-level docs.

Step 1: Determine ADR Title

Target: $ARGUMENTS

• If no title provided, ask the user for the ADR title
• Convert to kebab-case for the filename
• Check if docs/decisions/ directory exists; create it if missing

Step 2: Auto-Number

Find the next available ADR number:

find docs/decisions -name 'ADR-*.md' -not -name '.template.md' 2>/dev/null | sort | tail -1

• If no existing ADRs, start at 001
• Otherwise, take the highest number and add 1
• Format: ADR-NNN-<title>.md (e.g. ADR-001-use-postgresql.md)

Step 3: Gather Decision Details

Ask the user:

1. Context: What is the background? Why is a decision needed?
2. Options considered: What alternatives were evaluated? (at least 2)
3. Decision: Which option was chosen and why?
4. Consequences: What are the positive and negative impacts?
5. Status: Proposed, Accepted, Deprecated, or Superseded? (default: Accepted)

If the user provides minimal input:

• Read CLAUDE.md and docs/architecture.md for project context
• Read recent git log for related changes
• Infer context from the ADR title

git log --oneline -10 2>/dev/null

Step 4: Read Templates and Style Guide

Read the shared writing style guide and ADR template:

Read file: skills/project-scaffolder/references/writing-style-guide.md
Read file: skills/project-scaffolder/references/docs-templates.md

Follow all bilingual structure, formatting, and style rules from the writing style guide. Use the ADR Template section as the base structure.

Step 5: Create Bilingual ADR

Create docs/decisions/ADR-NNN-<title>.md with bilingual (English/Korean) structure:

# ADR-NNN: <Title in Natural Language>

<a href="#english"><img src="https://img.shields.io/badge/lang-English-blue.svg" alt="English"></a>
<a href="#korean"><img src="https://img.shields.io/badge/lang-한국어-red.svg" alt="Korean"></a>

---

<a id="english"></a>

# English

## Status
<Proposed | Accepted | Deprecated | Superseded>

## Context
<background explaining why a decision is needed>

## Options Considered

### Option 1: <Name>
- **Pros**: <advantages>
- **Cons**: <disadvantages>

### Option 2: <Name>
- **Pros**: <advantages>
- **Cons**: <disadvantages>

## Decision
<the decision that was made and the reasoning>

## Consequences

### Positive
- <positive impact>

### Negative
- <negative impact or trade-off>

## References
- <links to relevant docs, issues, or discussions>

---

<a id="korean"></a>

# 한국어

## 상태
<제안됨 | 승인됨 | 더 이상 사용되지 않음 | 대체됨>

## 배경
<결정이 필요한 이유를 설명하는 배경>

## 검토한 옵션

### 옵션 1: <이름>
- **장점**: <이점>
- **단점**: <단점>

### 옵션 2: <이름>
- **장점**: <이점>
- **단점**: <단점>

## 결정
<내려진 결정과 그 근거>

## 영향

### 긍정적
- <긍정적 영향>

### 부정적
- <부정적 영향 또는 트레이드오프>

## 참고 자료
- <관련 문서, 이슈, 또는 논의 링크>