MCCM Wiki
Glossary-first for domain prompts
Glossary-first prompting feeds the model your approved definitions for key terms before it drafts. Teams that skip this argue about words after every output and call it a model problem.
If “active customer,” “lead,” and “incident” mean three things in one company, a fluent draft will pick one at random and sound sure.
Build a short domain glossary
Ten to thirty terms beat a dictionary. Owner, date, definition, and a banned synonym list. Publish it where prompts live. Link uncommon terms to your public glossary when useful.
Inject definitions into the prompt
Paste the relevant three to five terms into the system or preamble. Instruct: use only these definitions. If a term is missing, ask. Do not invent.
Keep it versioned
When a definition changes, bump the prompt version and note it in the AI change log. Old outputs may be wrong under the new meaning. That is expected. Silence is not.
Quality signal
Reviewers spend less time rewriting definitions and more time on judgment. That is hours returned. Measure it.
MCCM practice
Pilots start by locking terms for the workflow. Ambiguous language is treated as a scope bug in the audit, not a training afterthought.
Related
MCCM Glossary · What an AI audit should deliver · From audit to pilot