What problem does it solve? Domain terminology drifts and design decisions get forgotten as a codebase evolves, leaving future readers guessing why things were built a certain way. This Skill actively sharpens a project's domain model during design conversations by challenging vague terms, cross-checking claims against code, and recording glossaries and decisions the moment they crystallize. ## Core Features & Use Cases - Glossary management: Creates and updates CONTEXT.md files with opinionated, tightly-defined domain terms, including explicit "avoid" lists for ambiguous synonyms. - Architecture Decision Records: Writes lightweight ADRs in docs/adr/ with sequential numbering, but only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - Multi-context support: Handles both single-context repos (one root CONTEXT.md) and multi-context repos via a CONTEXT-MAP.md that maps bounded contexts and their relationships. - Use Case: While discussing a billing feature, the user says "account" loosely; the Skill asks whether they mean Customer or User, updates CONTEXT.md with the resolved term, and offers an ADR when the team decides Billing communicates with Ordering via domain events instead of synchronous HTTP. ## Quick Start Help me sharpen the domain language for our ordering system and record any significant architectural decisions we make along the way.
