ubiquitous-language

To create a ubiquitous language glossary, the Skill extracts and formalizes domain terminology from your conversation into a structured UBIQUITOUS_LANGUAGE.md file. This output includes canonical definitions, aliases-to-avoid, relationships, flagged ambiguities, and an example dialogue to ensure terminology alignment.

Resolving ambiguous domain terms in DDD involves extracting an opinionated glossary from your conversation that identifies synonymous or overloaded concepts. The Skill flags conflicting usage, picks canonical terms, and documents aliases to avoid, ensuring everyone uses the same meanings.

Extracting canonical definitions for overloaded terms involves analyzing the conversation to pick preferred names and listing aliases to avoid when multiple words refer to the same concept. The Skill automates this by writing structured definitions and relationships to a markdown glossary.

Yes, you can generate a markdown glossary from an existing conversation. The Skill processes the current discussion to identify domain-relevant terms, flag ambiguities, and output a human-readable UBIQUITOUS_LANGUAGE.md file with canonical definitions and a short example dialogue.

You need to formalize domain terminology into a glossary when terms in your DDD or domain modeling discussions become ambiguous, synonymous, or overloaded. Formalizing prevents miscommunication by documenting canonical definitions and explicitly calling out conflicting usage.

A ubiquitous language glossary file contains canonical definitions, aliases-to-avoid, term relationships, flagged ambiguities, and a short example dialogue. It serves as a human-readable reference to maintain terminology alignment across the domain modeling process.