What problem does it solve? Architectural decisions made during coding sessions often live only in chat threads, PR comments, or memory, leaving future developers unable to understand why the codebase is shaped the way it is. This Skill records those decisions as structured ADR documents stored alongside the code. ## Core Features & Use Cases - Decision Detection: Recognizes explicit signals ("let's go with X", "record this as an ADR") and implicit signals (framework comparisons, database choices) during conversations. - Structured ADR Format: Generates Nygard-style ADRs with context, decision, alternatives considered, consequences, and lifecycle status (proposed, accepted, deprecated, superseded). - ADR Index Maintenance: Maintains a numbered log in docs/adr/ with an index README so past decisions are searchable when someone asks "why did we choose X?". - Use Case: During a session you decide to use PostgreSQL over MongoDB. The Skill drafts ADR-0002 with the rationale and rejected alternatives, asks for your approval, writes it to docs/adr/, and updates the index. ## Quick Start Tell the assistant to record the decision we just made about our database choice as an ADR.