What problem does it solve? Teams lose track of domain terminology and the reasoning behind architectural choices, leading to inconsistent language in code and repeated debates about settled decisions. This Skill actively builds a ubiquitous language glossary (CONTEXT.md) and records architectural decisions (ADRs) as they crystallize during design discussions. ## Core Features & Use Cases - Ubiquitous Language Management: Challenges conflicting terms, sharpens vague language, and updates CONTEXT.md inline with opinionated term definitions and avoided synonyms. - Architectural 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 decisions. - Use Case: While designing a billing feature, 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-based communication between Ordering and Billing contexts. ## Quick Start Ask the assistant to help define the domain terms for your project and record the architectural decisions made during the design discussion.
