What problem does it solve? Teams lose track of what domain terms mean and why hard-to-reverse decisions were made, because nobody remembers to write them down while design work is happening. This Skill detects those moments mid-workflow and records the settled vocabulary and reasoning as durable project artifacts. ## Core Features & Use Cases - Ubiquitous language glossary: Maintains a repo-root CONTEXT.md (or CONTEXT-MAP.md for multi-context projects) defining domain-specific terms, with rejected synonyms listed under Avoid. - Architecture decision records: Creates sequentially numbered ADRs in docs/adr/ using the adr-NNNN-<slug>-YYYY-MM-DD.md convention, gated by a three-part bar (hard to reverse, surprising without context, genuine trade-off). - Consent-gated writes: Detects the moment, proposes the entry, and writes only after the user approves, so it never creates spurious files. - Use Case: While grilling a design decision, the team settles on using Postgres over an event log. The Skill offers an ADR capturing the context, decision, and rejected alternative, then writes docs/adr/adr-0007-use-postgres-2026-07-23.md on approval. ## Quick Start Ask the agent to record the decision we just made about the database choice as an ADR and add the term we settled on to the project glossary.