Glossary and Terminology Governance Architect
Build governed glossaries with approved definitions, synonyms, deprecated terms, ownership, usage rules, translations, conflicts, and review cycles.
Glossary and Terminology Governance Architect is a free AI skill for docs & knowledge bases. Build governed glossaries with approved definitions, synonyms, deprecated terms, ownership, usage rules, translations, conflicts, and review cycles. It works with Claude, ChatGPT and is ready to use out of the box.
About this skill
Build governed glossaries with approved definitions, synonyms, deprecated terms, ownership, usage rules, translations, conflicts, and review cycles. It applies a structured workflow, labels assumptions, and produces implementation-ready guidance with ownership, controls, edge cases, and validation.
What it does
The skill analyzes goals, evidence, stakeholders, workflows, dependencies, constraints, and risks; converts them into a practical operating model; and produces explicit rules, responsibilities, exceptions, controls, tests, and rollout guidance.
What is included
- Governance context
- Domain and audience map
- Canonical glossary
- Synonyms and acronyms
- Deprecated terms
- Usage rules
- Translation guidance
- Ownership and approvals
How to use it
1. Download the glossary-and-terminology-governance-architect-SKILL.md file 2. Upload it to your AI, operational, or project workspace 3. Provide the current process, users, goals, evidence, and constraints 4. Add ownership, approval, risk, and implementation requirements 5. Use the output for design, review, testing, or rollout
Examples
Create a shared glossary for product, engineering, sales, support, analytics, and AI teams that currently use conflicting terms for users, accounts, workspaces, and agents.
A complete professional deliverable with context, decisions, ownership, workflows, edge cases, risks, controls, validation criteria, and an implementation roadmap.
FAQ
What is this skill for?
Will it invent facts or results?
Can it improve an existing process?
Does it include edge cases?
Can it assign ownership?
How is this different from generic advice?
Related Skills
Enterprise Taxonomy and Metadata Architect
Design taxonomies and metadata for documents, knowledge bases, products, and search with governance, ownership, and migration rules.
Knowledge Base Architect
Design a searchable, maintainable knowledge base with information architecture, templates, ownership, metadata, and content-governance rules.
Knowledge Base Content Lifecycle Manager
Manage knowledge-base content through creation, review, ownership, freshness, feedback, archiving, redirects, and performance measurement.