From fiddle
Create a new Architecture Decision Record in docs/technical/decisions/. Asks what was decided and why, writes the ADR file.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fiddle:adrThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a new Architecture Decision Record.
Create a new Architecture Decision Record.
ls docs/technical/decisions/*.md | grep -v template | sort -n | tail -1. Extract number, increment. If no existing ADRs, start at 001.docs/technical/decisions/NNN-kebab-case-title.md:# NNN — Title
**Date:** YYYY-MM-DD
**Status:** accepted
## Context
[2-3 sentences]
## Decision
[Concrete statement]
## Consequences
[Tradeoffs — what gets easier, what gets harder]
003-use-alloydb-over-cloudsql.mdsupersedes NNN.docs/technical/decisions/ doesn't exist, create it.npx claudepluginhub peel/fiddle --plugin fiddleCreates a numbered MADR ADR in `docs/adr/` documenting load-bearing architectural decisions (database, framework, auth model, integration choice). Prompts for context, decision, and alternatives, then updates the index.
Creates Architecture Decision Records (ADRs) with title, status, and MADR/basic/extended templates. Auto-numbers sequentially, prompts for context/options/rationale, writes to docs/decisions/ or docs/adr/.
Records concise Architecture Decision Records (ADRs) capturing what was decided and why, for decisions that are hard to reverse, surprising without context, or involve real trade-offs.