adr-createlisted

# adr-create Creates new ADR file with auto-numbering, fills Nygard template, updates dir's README.md index. --- ## Step 0 — Evaluate decision worthiness ### Phase A — Silent evaluation (always runs first) Assess decision across axes before engaging user: | Axis | What to assess | |------|----------------| | **Alternatives** | Obvious alternatives exist? Or was decision effectively forced? | | **Scope** | Crosses module/team/service boundaries — or local to one fn/file? | | **Reversibility** | Undoing costs significant? (data migration, API contract change, retraining) | | **Tradeoffs** | Context surface what was given up? | | **Existing ADRs** | Extends, contradicts, or supersedes prior choice? | **Clear verdict → act directly:** - **Clear yes** (cross-cutting, meaningful alternatives, non-trivial reversal cost, or intersects existing ADR): proceed to Step 1 without engaging user. - **Clear no** (routine impl detail, derivable from code, no alternatives in play, entirely local): inform user, suggest lighter alternative (inline comment, team note), stop. No escape hatch. **Inconclusive** (alternatives ambiguous, tradeoffs not surfaced, decision boundaries unclear) → Phase B. --- ### Phase B — Adversarial debate (only when Phase A inconclusive) Engage user to extract info Phase A couldn't resolve. Posture: adversarial-constructive. Argue against ADR necessity or framing until clear. State challenges directly; no softening. **Challenge axes** (raise 1–3 based on wha