What problem does it solve? Domain terminology drifts and key architectural decisions go unrecorded, leaving future readers guessing why the code looks the way it does. This Skill actively sharpens a project's domain model by challenging vague terms, resolving contradictions with the code, and writing down glossaries and decisions the moment they crystallize. ## Core Features & Use Cases - Glossary Management: Create and update CONTEXT.md files with opinionated, tightly-defined domain terms, including explicit "avoid" lists for ambiguous synonyms. - Architecture Decision Records: Write lightweight ADRs in docs/adr/ with sequential numbering, but only when a decision is hard to reverse, surprising, and the result of a real trade-off. - Multi-Context Support: Handle repos with multiple bounded contexts via a CONTEXT-MAP.md that lists contexts and their relationships. - 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 decides Ordering and Billing will communicate via domain events instead of synchronous HTTP. ## Quick Start Help me sharpen the domain language for our billing module and record the decision to use event-driven communication between contexts as an ADR.
