ubiquitous-language

Extract and formalize domain terminology into a merged glossary file.

12|2|Updated Nov 20, 2025

Search Tags:#glossary #disambiguation #ubiquitous-language #domain-terms #product-docs #discovery-docs

Ready to run

npx skills add https://github.com/alexandrbasis/claudops --skill ubiquitous-language-alexandrbasis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ubiquitous-language
Source: https://github.com/alexandrbasis/claudops/tree/main/.claude/skills/ubiquitous-language
Command: npx skills add https://github.com/alexandrbasis/claudops --skill ubiquitous-language-alexandrbasis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill extracts and formalizes domain terminology from conversations into a canonical glossary stored at product-docs/UBIQUITOUS_LANGUAGE.md, ensuring a shared vocabulary across planning docs, product docs, and code.

Core Features & Use Cases

Glossary extraction: Identifies domain nouns, verbs, and concepts from the current discussion.
Merging & disambiguation: Merges new terms with any existing glossary and flags ambiguities for resolution.
Documentation integration: Writes the merged glossary to product-docs/UBIQUITOUS_LANGUAGE.md for downstream use in PRD, JTBD, discovery, and code references.

Quick Start

Prompt the AI to extract and merge domain terms from the current conversation into product-docs/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 extract domain terminology from a conversation into a glossary?▼

To extract domain terminology into a glossary, prompt the AI to identify domain nouns, verbs, and concepts from your current conversation and write them into a structured markdown file for shared vocabulary.

What is a ubiquitous language glossary and when do I need one for product docs?▼

A ubiquitous language glossary is a canonical list of domain terms ensuring a shared vocabulary across planning, product docs, and code. You need one when disambiguating domain concepts across team discussions and downstream references.

How do I merge new domain terms with an existing glossary and resolve ambiguities?▼

Merging new domain terms with an existing glossary involves identifying overlapping definitions, flagging ambiguities for resolution, and propagating the updated terminology to related product and discovery docs.

Can I propagate glossary changes to PRD and discovery docs automatically?▼

Yes, glossary changes propagate to PRD, JTBD, and discovery docs by writing the merged content to a canonical markdown file, ensuring downstream documentation references the updated domain terms.

Do I need an existing product-docs directory to store the extracted domain glossary?▼

The skill ensures the glossary file exists at the product-docs directory path and writes the merged content there, creating the necessary structure for downstream use if it is not already present.

What is the best way to disambiguate domain terms across planning and code references?▼

The best way to disambiguate domain terms is extracting them into a canonical glossary file that flags conflicting definitions, ensuring consistent vocabulary propagation across product docs and code references.