What problem does it solve? Teams lose shared understanding of domain terminology and forget why architectural decisions were made, leading to inconsistent language in code and repeated debates. This Skill actively sharpens a project's domain model by challenging fuzzy terms, resolving contradictions with code, and recording decisions the moment they crystallize. ## 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, but only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - Active Language Sharpening: Challenges vague or conflicting terminology during design sessions and cross-references stated behavior against actual code to surface contradictions. - Use Case: While designing a billing feature, a user says "account" ambiguously; the Skill asks whether they mean Customer or User, updates CONTEXT.md with the resolved term, and offers an ADR when the team picks event-based communication between Ordering and Billing. ## Quick Start Ask the assistant to help define the domain terminology for your project and record it in a CONTEXT.md glossary as you discuss the design.
