What problem does it solve? Teams lose shared understanding of domain terminology and forget why key architectural decisions were made, leading to inconsistent language in code and repeated re-litigation of settled choices. This Skill actively sharpens a project's domain model during design discussions and records outcomes in CONTEXT.md glossaries and ADR files. ## Core Features & Use Cases - Ubiquitous Language Management: Challenges conflicting or fuzzy terms in conversation and updates CONTEXT.md inline with canonical definitions and terms to avoid. - Architecture Decision Records: Offers ADRs only when decisions are hard to reverse, surprising without context, and the result of real trade-offs, using a minimal numbered format in docs/adr/. - Multi-Context Support: Handles single-context repos with one CONTEXT.md or multi-context repos via a CONTEXT-MAP.md linking per-context glossaries and decision logs. - Use Case: While designing an ordering system, the user says "account" ambiguously; the Skill asks whether they mean Customer or User, records the resolved term in CONTEXT.md, and drafts an ADR when the team picks event-sourced orders over a CRUD model. ## Quick Start Ask the assistant to help define the domain terms for your project and record them in a CONTEXT.md glossary as you discuss the design.
