What problem does it solve? Teams lose track of why architectural choices were made, and ad-hoc decision notes become inconsistent or get edited after the fact. This Skill records Architecture Decision Records in a consistent, auto-numbered, immutable format so the reasoning behind non-obvious decisions stays discoverable. ## Core Features & Use Cases - Scaffold new ADRs: Auto-numbers the next NNNN file, slugs the title, and renders the MADR-lite template (Status / Context / Decision / Alternatives / Consequences) under docs/adr/. - List the decision log: Shows number, status, and title for every ADR, with optional JSON output for scripting. - Supersede decisions: Flips an old ADR to Superseded with a link to its successor and scaffolds the replacement with a back-pointer, preserving immutability. - Use Case: After choosing PostgreSQL over DynamoDB for a service, run the skill to create an ADR capturing the context, trade-offs, and consequences so future reviewers understand the decision without re-litigating it. ## Quick Start Ask the assistant to create a new ADR titled "Use PostgreSQL for the billing service" with status Accepted in the current repository.