What problem does it solve? Teams lose alignment when domain terms drift and architectural decisions go unrecorded, leading to inconsistent code and repeated debates. This Skill actively sharpens a project's domain model by challenging fuzzy terminology, resolving contradictions between language and code, and capturing 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. - ADR Authoring: Record hard-to-reverse architectural decisions in numbered ADR files under docs/adr/, only when decisions are surprising, irreversible, and involve real trade-offs. - Multi-Context Support: Handle repos with multiple bounded contexts via a CONTEXT-MAP.md that maps contexts and their relationships. - Use Case: While designing an ordering system, the user says "account" — the Skill asks whether they mean Customer or User, updates CONTEXT.md with the resolved term, and offers an ADR when the team decides Ordering and Billing communicate via domain events instead of synchronous HTTP. ## Quick Start Ask the assistant to help define the domain terms for your project and record them in a CONTEXT.md glossary.
