ubiquitous-language

To extract a DDD ubiquitous language glossary, the Skill scans your conversation to identify domain terms, synonyms, and ambiguities, then generates an opinionated glossary with canonical definitions and aliases to avoid.

Resolving domain terminology ambiguity involves flagging where the same word maps to multiple concepts and where different words refer to the same concept, then choosing preferred canonical terms to ensure consistency across product and engineering teams.

You generate a shared domain vocabulary by asking the Skill to process your discussion, which produces an updated UBIQUITOUS_LANGUAGE.md file containing canonical definitions, flagged ambiguities, and an example dialogue for your team.

You need to formalize domain model terminology when domain confusion arises from overlapping terms, requiring you to extract domain-relevant nouns and verbs to harden terminology and establish a shared vocabulary for DDD boundaries.

Yes, you can align product and engineering experts by producing a reusable DDD-style ubiquitous language glossary that lists preferred terminology and aliases to avoid for consistency across domain experts, product, and engineering.