What problem does it solve? Domain terminology drifts and architectural decisions get forgotten, leaving future readers guessing why the code looks the way it does. This Skill actively sharpens a project's domain model by challenging fuzzy terms, stress-testing concepts with concrete scenarios, and recording decisions the moment they crystallize. ## Core Features & Use Cases - Ubiquitous Language Management: Maintains an opinionated CONTEXT.md glossary with canonical terms and explicit _Avoid_ lists, updated inline as terms are resolved. - Architectural Decision Records: Creates numbered ADRs in docs/adr/ only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - Multi-Context Support: Detects CONTEXT-MAP.md for multi-context repositories and routes terms and decisions to the correct bounded context. - Use Case: While designing an ordering system, the user says "account" ambiguously; the Skill challenges the term, resolves it to Customer versus User, updates CONTEXT.md immediately, and offers an ADR when the team picks event-sourced writes over a CRUD model. ## Quick Start Ask the assistant to use the domain-modeling skill to define the term "cancellation" in CONTEXT.md and record why we chose event sourcing as an ADR.
