ubiquitous-language

To extract a ubiquitous language glossary, apply the skill to your domain conversation to generate a structured UBIQUITOUS_LANGUAGE.md file containing canonical definitions, aliases to avoid, and example dialogue.

Standardizing domain terminology for DDD involves identifying domain nouns and concepts, selecting opinionated canonical terms, and listing conflicting synonyms as aliases to avoid in a shared markdown glossary.

Detecting ambiguous terminology in business requirements is done by flagging where a single word represents multiple concepts, then proposing canonical domain terms to explicitly distinguish them in your documentation.

Yes, you can resolve conflicting synonyms in domain models by capturing relationships and cardinality between terms, choosing canonical terms, and documenting the discarded aliases within a centralized glossary file.

You need a ubiquitous language glossary when your team discusses domain models or business concepts and requires consistent terminology to resolve ambiguous definitions and communicate with a shared understanding.

Generating a glossary this way captures lifecycle clarity by mapping relationships and cardinality between domain terms, while also including a small example dialogue demonstrating correct canonical usage.