What problem does it solve? Teams lose shared understanding of domain terminology as codebases grow, leading to ambiguous terms, contradictory code, and undocumented architectural decisions. This Skill keeps the project's domain glossary and decision records accurate by challenging fuzzy language and capturing resolutions the moment they happen. ## Core Features & Use Cases - Glossary Maintenance: Challenge terms against docs/resources/CONTEXT.md, sharpen vague language into canonical terms, and update the glossary inline as terms are resolved. - Scenario Stress-Testing: Invent edge-case scenarios to probe domain relationships and cross-reference stated behavior against actual code to surface contradictions. - Selective ADR Recording: Offer Architecture Decision Records only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - Use Case: While designing an order system, a user says "cancel the account" — the Skill flags that the glossary defines cancellation for Orders, not Customers, proposes precise terms, updates CONTEXT.md, and offers an ADR for the partial-cancellation trade-off. ## Quick Start Ask the agent to review the domain terminology in docs/resources/CONTEXT.md and record any newly resolved terms or architectural decisions as we discuss the order cancellation flow.
