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, versioned ADR documents alongside the code. ## Core Features & Use Cases - Decision Detection: Recognizes explicit signals ("let's record this decision") and implicit signals (choosing between frameworks, databases, or patterns) during conversations. - Structured ADR Format: Generates lightweight Nygard-style ADRs with context, decision, alternatives considered, and consequences sections. - ADR Index & Lifecycle: Maintains a numbered ADR log in docs/adr/ with an index table and status lifecycle (proposed, accepted, deprecated, superseded). - Use Case: After deciding to use PostgreSQL over MongoDB for your primary datastore, ask the assistant to record the decision; it drafts ADR-0002 with rationale and rejected alternatives, then writes it to docs/adr/ after your approval. ## Quick Start Ask the assistant to record the decision we just made about our database choice as an ADR.