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 captures terms in a CONTEXT.md glossary and records trade-offs as ADRs the moment they crystallize. ## Core Features & Use Cases - Glossary Management: Creates and updates CONTEXT.md files with opinionated term definitions, including Avoid lists for rejected synonyms, supporting both single-context and multi-context repos via CONTEXT-MAP.md. - Architecture Decision Records: Writes numbered ADRs in docs/adr/ using a minimal template, offered 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 discussion, stress-tests domain relationships with concrete edge-case scenarios, and cross-references claims against the actual code. - Use Case: While designing an ordering system, a 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 picks event-sourced orders over a CRUD model. ## Quick Start Ask the assistant to help define the domain terms for your project and record them in a CONTEXT.md glossary.
