What problem does it solve? Teams lose track of why decisions were made and use inconsistent terminology across a codebase, causing confusion and repeated debates. This Skill captures domain language in a CONTEXT.md glossary and records significant trade-offs as lightweight ADRs the moment they crystallize. ## Core Features & Use Cases - Glossary Management: Creates and updates CONTEXT.md files with opinionated term definitions, including avoided synonyms and multi-context maps via CONTEXT-MAP.md. - Architecture Decision Records: Writes numbered ADRs in a decisions/ directory, 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 discussions and cross-references claims against the actual code. - Use Case: While designing an ordering system, the user says "account" ambiguously; the Skill prompts them to distinguish Customer from User, records the resolved term in CONTEXT.md, and drafts an ADR when they choose event-sourced writes over a CRUD model. ## Quick Start Ask the agent to help define the domain terms for your project and record the key architectural decisions as ADRs.
