dev-util-glossary

Extract and formalize domain terminology from conversations into GLOSSARY.md.

Updated Jun 17, 2025
One-click install
npx skills add https://github.com/nikbrunner/dots --skill dev-util-glossary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-util-glossary
Source: https://github.com/nikbrunner/dots/tree/main/common/.agents/skills/dev-util-glossary
Command: npx skills add https://github.com/nikbrunner/dots --skill dev-util-glossary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This glossary tool extracts and formalizes domain terminology from conversations, saving it to GLOSSARY.md and reducing ambiguity.

Core Features & Use Cases

  • Canonical terminology: identifies domain terms and records precise definitions with suggested aliases to avoid confusion.
  • Ambiguity flagging: detects conflicting or overloaded terms and surfaces clarifications.
  • Guided collaboration: provides a ready-to-use glossary structure for product and domain discussions.

Quick Start

Generate a domain glossary from the current conversation and save it as GLOSSARY.md.

Frequently Asked Questions about dev-util-glossary

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

FAQPage Schema
How do I extract domain terminology from a conversation to build a ubiquitous language glossary?

To build a ubiquitous language glossary, this Skill analyzes your current conversation to identify domain terms, records precise definitions, and saves the formalized terminology directly to a GLOSSARY.md file.

What is the best way to document domain terms and handle terminology ambiguity during requirements gathering?

Handling terminology ambiguity during requirements gathering is done by detecting conflicting or overloaded domain terms, surfacing clarifications, and recording canonical definitions with suggested aliases to reduce confusion.

How do I maintain and update a domain glossary as the dialogue evolves?

You can update a domain glossary as dialogue evolves by continuously applying prescribed formatting rules to extract new terms, group terminology logically, and append changes to the existing GLOSSARY.md file.

Can I use a glossary generator to flag synonyms and overloaded terms in domain modeling discussions?

Yes, you can use this glossary generator during domain modeling to flag synonyms and overloaded terms, resolving ambiguity by establishing canonical terminology and grouping related domain terms within the output file.

Does this domain glossary tool require any specific dependencies or components to function?

No specific dependencies or components are required to function, as this Skill operates independently to analyze dialogue and write the extracted domain terminology with prescribed formatting directly to your project.

What limitations exist when extracting domain modeling terms from unstructured dialogue?

A key limitation is that extracting domain modeling terms relies entirely on the current conversation's context, meaning the resulting GLOSSARY.md is only as comprehensive and accurate as the dialogue analysis provided to it.