docs-create-adr

name	Docs: Create ADR
description	{{ ƔƔƔ }} Create an Architecture Decision Record (ADR) for a significant technical decision
when_to_use	When a technical choice was hard-won or non-obvious enough that future-you (or a teammate) will ask 'why did we do it this way?' — schema shape, library swap, architectural pattern.
model	sonnet
disable-model-invocation	true
allowed-tools	["Read","Glob","Grep","Write"]
argument-hint	["brief decision title"]

Guide user through creating an ADR via focused questions, then generate using ~/.claude/library/templates/ADR.md ~/.claude/library/templates/ADR.md 1. Read ADR template 2. Ask focused questions conversationally (not all at once): - Context: What problem/decision? What factors? Constraints? - Decision: What did you choose? Be specific. - Alternatives: What else considered? Pros/cons? Why rejected? - Consequences: What improves? What trade-offs? What gets harder? 3. Generate ADR with proper numbering (check existing in docs/dev/architecture/) 4. Suggest location: docs/dev/architecture/[decision-slug]-adr.md 5. Show for approval; revise if needed - Keep questions conversational - Probe for details if answers incomplete - ADR should be understandable 6 months later