What problem does it solve? Teams lose shared understanding of domain terminology and forget why architectural decisions were made, leading to inconsistent language in code and repeated debates over settled trade-offs. ## Core Features & Use Cases - Ubiquitous Language Management: Challenge conflicting terms, sharpen vague language, and record resolved terms in a CONTEXT.md glossary with preferred words and terms to avoid. - Architectural Decision Records: Offer and write lightweight 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: Handle single-context repos with one CONTEXT.md or multi-context repos via a CONTEXT-MAP.md linking per-context glossaries and ADRs. - 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 use the domain-modeling skill to pin down the term "cancellation" in CONTEXT.md and record why we chose Postgres for the write model as an ADR.
