adrlisted

# ADR Skill: Architecture Decision Record Management ## Overview This skill enables systematic creation, maintenance, and enforcement of Architecture Decision Records. ADRs document significant architectural choices along with their context, alternatives considered, and consequences. They serve as living documentation so current and future developers (and AI agents) understand why the system is built the way it is. The skill bundles three patterns that distinguish it from a basic ADR template: 1. **Anti-Rationalization Guards**: a table of excuses agents and humans use to skip writing an ADR, paired with counter-arguments. Pre-flight discipline. 2. **Verification Gates**: four named gates an ADR must pass before its Status flips from `Proposed` to `Accepted`. Reviewers can block on a single named gate. 3. **Human Decision Documentation**: explicit `Decision Maker:` attribution so user-driven choices are visible in the record, distinct from agent-generated ADRs. --- ## When to Use ### Automatic triggers Use this skill automatically when: - Reviewing a PR or analysing code changes for architectural impact. - A change introduces a new pattern, dependency, or contract. - Refactoring proposals affect system design. - A user asks an architectural question ("why did we choose X?", "should we use Y or Z?"). ### Explicit triggers Use this skill when the user mentions: - "Create an ADR" / "Document this decision" / "Architecture decision". - "Why did we choose...?" / "What