What problem does it solve? Conversations about a product or system often use overloaded or inconsistent terms ("account", "user", "customer"), causing misalignment between developers and domain experts. This Skill turns an ongoing conversation into a DDD-style ubiquitous language glossary with canonical terms, tight definitions, and flagged ambiguities. ## Core Features & Use Cases - Term Extraction and Canonicalization: Scans the conversation and attached docs for domain-relevant nouns and verbs, picks one canonical term per concept, and lists aliases to avoid. - Ambiguity Detection: Identifies words used for multiple concepts and synonyms used for the same concept, recording them in a "Flagged ambiguities" section. - Living Glossary File: Writes or updates DOMAIN_GLOSSARY.md with grouped term tables, a Relationships section, and an example dialogue; re-runs merge new terms and mark entries as "(new)" or "(updated)". - Use Case: During a fintech project kickoff, run the skill after a requirements discussion to produce a shared glossary distinguishing Account, Workspace, and Session before writing the domain model. ## Quick Start Ask the assistant to run the domain-glossary skill on the current conversation to generate a DOMAIN_GLOSSARY.md file with canonical terms and definitions.
