What problem does it solve? Teams lose shared understanding of domain terminology and forget why key architectural decisions were made, leading to inconsistent language in code and repeated re-litigation of settled trade-offs. This Skill actively sharpens a project's domain model during design discussions and captures terms 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 without context, 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, their locations, and their relationships. - Use Case: While designing a billing feature, the user says "account" loosely. The Skill challenges the term, distinguishes Customer from User, updates CONTEXT.md inline, and offers an ADR when the team decides Billing communicates with Ordering via domain events instead of synchronous HTTP. ## 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.
