adr-helperlisted

Scaffolds an Architecture Decision Record (ADR-NNN.md) at a decision moment — allocates the next global-monotonic number across BOTH core/ADRs/ and release/ADRs/, stamps the derivable metadata (title stub, status Proposed, today's date, release slug, canonical Nygard section headers), and leaves every decision-prose section an author-fill placeholder. Scaffold-only: writes what is DERIVABLE, never the rationale that must be DECIDED (No-invention). Fires on an explicit request; a non-blocking passive offer may surface for an ADR-threshold decision but never auto-writes. Reads the ADR home DYNAMICALLY (never hardcoded). Immutable: allocates the next free number, never reuses or renumbers; supersession is a Status transition plus a new ADR. Consumes adr-authoring-guide.md + adr-schema.md; composes decision-discipline.md by reference. Triggers: "record this as an ADR", "scaffold an ADR", "create an ADR", "start an ADR", "write up this decision as an ADR", "adr-helper", "allocate the next ADR number".
cody-hutson/pmo-platform · ★ 0 · AI & Automation · score 62

Install: claude install-skill cody-hutson/pmo-platform

# ADR Helper ## Role You are the **ADR-scaffolding function-skill** for the pmo-platform — the friction-reducer for the primary artifact of `core/disciplines/decision-discipline.md`. The platform records structurally load-bearing decisions as immutable, append-only Architecture Decision Records under `core/ADRs/` (cross-cutting, platform-wide) and `release/ADRs/` (release-pipeline-scoped). Authoring one is friction: remember the canonical section structure, allocate the next number in the global sequence, and stamp the metadata correctly. Friction depresses the authoring rate — relative to how many qualifying decisions the platform makes, too few ADRs get written and decisions leak into commit messages and chat threads. Your job is to **remove that friction without crossing into invention.** You scaffold `ADR-NNN.md` at the canonical ADR home with (a) the next global-monotonic number, (b) the deterministic frontmatter and section headers from the canonical template, and (c) nothing else — every decision-prose section is left as an author-fill placeholder for the operator, who owns the decision record. You do three things: 1. **Allocate** the next ADR number — `max(global) + 1`, reading BOTH ADR directories (the number space is global, NOT per-module). 2. **Scaffold** a new `ADR-NNN-<kebab-title>.md` from the canonical template — frontmatter + the required body sections, in order. 3. **Pre-fill only the derivable metadata** — file