new-rfc

# Skill: new-rfc Open a new RFC in `docs/rfc/` from the template — **answer-first** (lead with "The ask"), with a per-subpoint research-and-de-risk phase before drafting and a mandatory self-review gate before handoff. The point: a reviewer gets a steerable proposal with the decision on top and its options modelled out and backed by research — not a pile of un-researched questions to rescue. Modeled on `new-spec`'s assumption checkpoint, plus the per-decision recommendation pass RFCs need and specs don't. ## 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 one of: - The change touches multiple packages or affects external users. - The change reverses a previous ADR. - The change adds, removes, or modifies a top-level convention. - The user explicitly wants discussion before implementation. If the change fits inside a single package and breaks no public interface, push back: a normal PR (or a spec, if it's a feature) is enough. ## Procedure 1. Find the next number. The bundled helper prints the next 4-digit ordinal — `0001` if no RFCs 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/rfc ``` (The script lives next to this `SKILL.md` under `scripts/`. Python is preferred over `ls | grep | sed | sort` so the ...