What problem does it solve? After a long design discussion, domain terminology drifts: one word ends up meaning two things, or two words mean the same thing, and the project glossary falls behind. This Skill retrospectively scans the current conversation, detects ambiguities and synonyms, and consolidates canonical domain terms into the project's CONTEXT.md glossary. ## Core Features & Use Cases - Conversation Term Harvesting: Scans the current conversation for domain-relevant nouns, verbs, and concepts, skipping generic programming terms. - Ambiguity Detection: Flags cases where one word covers multiple concepts or multiple words cover one concept, and proposes an opinionated canonical term with aliases to avoid. - Glossary Consolidation: Writes agreed terms into docs/resources/CONTEXT.md following the domain-modeling format, extending existing definitions rather than duplicating them. - Use Case: After a two-hour design session about billing, run this Skill to catch that "account" and "customer" were used interchangeably, propose "customer" as canonical, and update the glossary's Relationships and Flagged ambiguities sections. ## Quick Start Review this conversation and update the project glossary in docs/resources/CONTEXT.md with the domain terms we used, flagging any ambiguities.
