adr-create

# adr-create ## When to use Use this skill when: - A non-trivial architectural choice needs a written record (kernel membership, cap raises, contract changes, library swap, deprecation). - A decision overrides a previous one and needs `supersedes:` linkage. - A roadmap phase closes and the chosen variant must be cited. - The user says "write an ADR for X", "decision log this", "we need a record of why we picked Y". Do NOT use when: - The change is reversible without governance impact (typo, lint fix, refactor that stays inside one module). - The decision is already covered by an existing ADR — extend or supersede it instead of duplicating. - A skill, rule, or guideline is the better home (use those skills). ## Goal - Sequential `ADR-NNN-<slug>.md` numbering with no gaps. - Standard template: Status, Context, Decision, Consequences, Alternatives, References. - Regenerated index so readers find the ADR by topic, not by ls. - Zero MCP-tool dependency — pure filesystem + TypeScript tooling (run via ./scripts-run). ## Preconditions - An ADR directory exists. Two layouts coexist (see [`docs/contracts/adr-layout.md`](../../../docs/contracts/adr-layout.md)): - **Flat** — `docs/decisions/` (or `docs/adr/` alias): cross-cutting governance ADRs, 3-digit numbering (`ADR-NNN-<slug>.md`). - **Per-area** — `docs/adrs/<area>/`: sub-area ADRs, 4-digit numbering (`NNNN-<slug>.md`); `<area>` must match the canonical inventory in [`scripts/audit_adr_coverage....