ubiquitous-language

Extract domain terms from conversations and generate a markdown glossary with flagged ambiguities.

88|9|Updated Jul 16, 2020
One-click install
npx skills add https://github.com/docs-plus/docs.plus --skill ubiquitous-language-docs-plus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ubiquitous-language
Source: https://github.com/docs-plus/docs.plus/tree/main/.agents/skills/ubiquitous-language
Command: npx skills add https://github.com/docs-plus/docs.plus --skill ubiquitous-language-docs-plus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In software development, inconsistent or ambiguous domain terminology between developers and domain experts leads to miscommunication, incorrect implementations, and costly rework. This Skill solves that by formalizing shared domain language from existing conversations.

Core Features & Use Cases

  • Term Extraction: Scans conversations to identify domain-relevant nouns, verbs, and concepts.
  • Ambiguity Flagging: Detects overloaded terms (one word for multiple concepts) and synonyms (multiple words for one concept), proposing canonical terms.
  • Structured Glossary Generation: Creates a formatted markdown glossary with definitions, term relationships, and example dialogues for stakeholder alignment.
  • Use Case: Use this when building a domain-driven design (DDD) system to ensure all team members use consistent terminology for core domain concepts like "Order", "Customer", and "Invoice".

Quick Start

Use the ubiquitous-language skill to extract a domain glossary from our discussion about the e-commerce order management system, flag any ambiguous terms, and save the output to UBIQUITOUS_LANGUAGE.md.

Frequently Asked Questions about ubiquitous-language

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a ubiquitous language glossary for domain-driven design?

To create a ubiquitous language glossary for domain-driven design, extract domain-relevant nouns and verbs from team conversations, flag ambiguous synonyms, and map term relationships into a structured markdown file.

What is ubiquitous language in DDD and why is ambiguous terminology a problem?

Ubiquitous language in DDD is a shared, rigorous vocabulary used by developers and domain experts. Ambiguous terminology causes miscommunication and incorrect implementations, which formalizing a canonical glossary eliminates.

How do I identify and resolve domain terminology ambiguities in software specifications?

Resolve domain terminology ambiguities by scanning specification discussions to detect overloaded terms and synonyms, then proposing canonical terms with definitions and example dialogues for stakeholder alignment.

Can I generate a structured domain model glossary directly from team conversations?

Yes, you can generate a structured domain model glossary directly from conversations by extracting domain concepts, flagging inconsistent language, and saving canonical definitions with relationship mappings to a markdown file.

What is the best way to align developer and domain expert terminology during software development?

The best way to align developer and domain expert terminology is to formalize shared domain language by extracting concepts from discussions, flagging ambiguities, and generating a structured markdown glossary for reference.