What problem does it solve? Teams lose track of domain terminology and the reasoning behind architectural decisions, leading to inconsistent language in code and repeated debates about settled choices. This Skill actively sharpens a project's domain model during design discussions by maintaining a canonical glossary (CONTEXT.md) and recording significant decisions as ADRs. ## Core Features & Use Cases - Glossary Management: Creates and updates CONTEXT.md files with opinionated term definitions, including terms to avoid, supporting both single-context and multi-context repositories via CONTEXT-MAP.md. - Architecture Decision Records: Writes lightweight ADRs in docs/adr/ with sequential numbering, offered only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - Language Sharpening: Challenges vague or conflicting terminology during conversations, stress-tests domain relationships with concrete edge-case scenarios, and cross-references claims against actual code. - 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 Help me define the domain terms for our ordering system and record the key architectural decisions we just made as ADRs.
