What problem does it solve? Architecture decisions made in conversations or pull requests get lost, and future contributors re-litigate settled trade-offs. This Skill captures each decision as a durable, one-page ADR so the rationale survives. ## Core Features & Use Cases - Nygard-format ADRs: Produces the five standard sections (title, Status, Context, Decision, Consequences) with rejected alternatives listed as one-clause bullets. - Strict style enforcement: One decision per file, one page maximum, mandatory downside, no code references, no dates, no diagrams, and qualitative findings instead of exact counts. - Filing and lifecycle management: Files ADRs as docs/adr/NNNN-kebab-title.md with zero-padded numbering, and manages the Proposed to Accepted to Superseded status lifecycle. - Use Case: After a design discussion settles on adapting registry auth from e2e parameters, ask for an ADR and get a concise record with the rejected alternatives and the accepted cost, ready to commit. ## Quick Start Ask the assistant to write an ADR recording the design decision we just made about the chosen approach.
