What problem does it solve? Architectural rulings made in chat, reviews, or meetings get lost, re-litigated, or silently contradicted by later changes. This Skill keeps durable decisions in a versioned decisions/ folder with a defined lifecycle so every change can be checked against what was actually agreed. ## Core Features & Use Cases - Consult before changing: List accepted records whose applies-to globs match the paths you are touching, and cite them on work items, pull requests, and Decision: commit trailers. - Author and accept records: Apply a significance test, pass a completeness gate (options considered, default if unanswered, timeline, scope), write Done when / Verify by criteria, and record a named human decider on acceptance. - Supersede safely: Replace accepted decisions with two-way supersedes/superseded-by pointers, sweep stale citations, and regenerate the index so records stay discoverable. - Use Case: Before modifying a public API contract, consult decisions/ for binding records, discover one that forbids the change, and open a superseding record with a named decider instead of shipping a silent contradiction. ## Quick Start Check the decisions folder for any accepted records that apply to the files I am about to change, and draft a new decision record if this change settles a significant architectural question.
