new-adr

# Skill: new-adr Create a new ADR in `docs/adr/` from the template, with the next sequential number. ## Output rendering Key–value / one record — For a single record's fields, use an aligned key: value list, not a two-row table. ## When to invoke Before invoking, confirm: 1. The decision is about *architecture or shared infrastructure*, not a single feature's internals (that's a spec). 2. The decision has been *made or is being formally proposed*. ADRs are not a venue for open-ended discussion — that's an RFC. 3. There is a *concrete tradeoff* — at least one viable alternative was considered. If there's only one option, you don't need an ADR. 4. The record is *one decision wide*. If you're packing three or more load-bearing sub-decisions into a single ADR, stop and ask whether this is really one decision — or an umbrella that should be an RFC spawning several smaller ADRs. For an ADR, *complete* is not *exhaustive*: the RFC carries the debate, the ADR records the durable outcome. If any of these checks fail, push back rather than proceeding. ## Procedure 1. Find the next number. The bundled helper prints the next 4-digit ordinal — `0001` if no ADRs exist yet, max-plus-one otherwise. It parses the full digit prefix, so a `00099-foo.md` correctly yields `0100` (not `0010`): ```bash python3 scripts/next-ordinal.py docs/adr ``` (The script lives next to this `SKILL.md` under `scripts/`. Python is preferred over `ls | grep | ...