What problem does it solve? Teams lose the reasoning behind architectural choices over time, leaving future maintainers unable to understand why a system was built a certain way. This Skill captures settled decisions as frozen, dated ADR documents with context, rejected alternatives, and honest consequences. ## Core Features & Use Cases - Structured ADR authoring: Creates numbered records (NNNN-title.md) from a template with exactly Context, Decision, and Consequences sections, plus frontmatter for status, deciders, and supersedes chains. - Supersedes chain management: Wires replacement decisions in both directions, flipping the old record to superseded status without rewriting its frozen prose. - Prior-art scanning: Searches existing decisions and proposals before writing to surface contradictions and link parent proposals. - Use Case: After a team agrees to adopt event sourcing for the orders service, use this Skill to scan prior decisions, allocate the next ADR number, record the rejected alternatives, and supersede the old REST-based decision. ## Quick Start Record the decision we just made to adopt event sourcing for orders as an ADR, superseding the old REST API decision.