What problem does it solve? Teams lose track of domain terminology and the reasoning behind architectural choices, leading to inconsistent language in code and repeated debates about settled decisions. 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, supporting both single-context and multi-context repos 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 a billing feature, 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-based communication between Ordering and Billing. ## Quick Start Help me define the domain language for our ordering system and record any significant architectural decisions we make along the way.
