What problem does it solve? Teams lose alignment when domain terms drift, vocabulary stays fuzzy, and the reasoning behind architectural choices is forgotten. This Skill keeps a project's domain model sharp by capturing terminology in a CONTEXT.md glossary and recording significant decisions as ADRs the moment they crystallize. ## Core Features & Use Cases - Ubiquitous Language Management: Challenges conflicting terms, sharpens vague vocabulary, and updates CONTEXT.md inline as terms are resolved, with support for single-context and multi-context repos via CONTEXT-MAP.md. - Architectural Decision Records: Offers ADRs in docs/adr/ only when a decision is hard to reverse, surprising without context, and the result of a real trade-off, using a minimal sequential-numbered format. - Scenario Stress-Testing: Invents concrete edge-case scenarios and cross-references claims against the actual code to surface contradictions between the stated model and the implementation. - Use Case: While designing an ordering system, the user says "account" loosely; the Skill asks whether they mean Customer or User, records the resolved term in CONTEXT.md, and offers an ADR when the team picks event-sourced writes over a CRUD model. ## Quick Start Ask the agent to use the domain-modeling skill to define the term "Order" in CONTEXT.md and record why the team chose Postgres for the write model as an ADR.
