What problem does it solve? Teams lose shared understanding of domain terminology over time: the same concept gets multiple names, code drifts from the intended model, and key architectural decisions are forgotten. This Skill actively builds and sharpens the project's domain model during design discussions, capturing terms and decisions the moment they crystallize. ## Core Features & Use Cases - Glossary Management: Challenges conflicting or fuzzy terminology against CONTEXT.md, proposes precise canonical terms, and updates the glossary inline as terms are resolved. - ADR Authoring: Offers Architecture Decision Records only when a decision is hard to reverse, surprising without context, and the result of a real trade-off, using a minimal one-paragraph format. - Multi-Context Support: Handles both single-context repos (one root CONTEXT.md) and multi-context repos via a CONTEXT-MAP.md pointing to per-context glossaries and ADR directories. - Use Case: While designing a billing feature, the user says "account" ambiguously; the Skill asks whether they mean Customer or User, records the resolved term in CONTEXT.md, and drafts an ADR when the team decides Billing communicates with Ordering via domain events instead of synchronous HTTP. ## Quick Start Ask the agent to help define the domain terminology for your project and record the key architectural decisions as ADRs.
