What problem does it solve? Domain language drifts as projects grow: terms get overloaded, decisions lose their rationale, and code diverges from how the team talks about the system. This Skill actively sharpens a project's domain model by challenging fuzzy terminology, cross-checking claims against code, and recording glossary entries and architecture decisions the moment they crystallize. ## Core Features & Use Cases - Glossary Management: Creates and updates CONTEXT.md files with precise canonical terms, flagging conflicts between how users speak and what the glossary defines. - Architecture Decision Records: Writes ADRs in docs/adr/ when decisions are hard to reverse, surprising without context, and the result of genuine trade-offs. - Multi-Context Support: Handles repositories with multiple bounded contexts via CONTEXT-MAP.md, keeping context-specific glossaries and ADRs in their own directories. - Use Case: While designing an order system, a user says "cancel the account." The Skill asks whether they mean the Customer or the User, checks whether the code supports partial cancellation, updates CONTEXT.md with the resolved term, and offers an ADR for the cancellation policy decision. ## Quick Start Ask the assistant to help define the domain terminology for your project and record it in a CONTEXT.md glossary as terms are resolved.
