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 avoided synonyms, for single or multi-context repositories via CONTEXT-MAP.md. - Architecture Decision Records: Writes numbered ADRs in docs/adr/ only when decisions are hard to reverse, surprising without context, and the result of real trade-offs. - Language Sharpening: Challenges vague or conflicting terminology during design sessions and cross-references stated behavior against 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 offers an ADR when the team picks event-sourced writes 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 as you discuss the design.
