Domain Vocabulary Modeling
Create a traceable proposed language model for the domain.
Workflow
- Name the scope, intended users, and authoritative evidence sources.
- Extract terms as they are actually used. Preserve conflicting definitions and overloaded words.
- For each concept, record
Term, Proposed definition, Evidence, Examples, Non-examples, Relationships, Invariants, Authority, and Status.
- Separate business concepts from storage names, API fields, UI labels, implementation classes, and vendor terminology.
- Identify synonyms, homonyms, missing concepts, ambiguous boundaries, and terms whose meaning changes by context.
- Test the model against representative scenarios and existing interfaces. Record contradictions rather than silently choosing a definition.
- Mark every entry as observed, proposed, ratified, rejected, or unresolved. Name the decision owner for ratification when known.
Boundaries
- Do not rename code, schemas, or public interfaces without separate implementation authority.
- Do not declare a proposed definition canonical from repetition alone.
- Keep private product language in its owning repository or private overlay.
Output
Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.
Return the vocabulary table, relationship notes, contradictions, ratification needs, and migration implications.
Example
Synthetic example; not an observed client result.
Input: Sales uses account for a company; billing uses it for a payment ledger.
Output: Define separate Company and Billing Account concepts, with an explicit relationship. These are proposed terms until the domain owners confirm them.
1---2name: model-domain-vocabulary3description: "Clarifies domain terms when teams use the same word differently or code and documents disagree; proposes definitions and examples without declaring owner approval."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/model-domain-vocabulary7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-workflows"10 invocation: "implicit"11 provenance: "original"12 risk_class: "read-only"13---1415# Domain Vocabulary Modeling1617Create a traceable proposed language model for the domain.1819## Workflow20211. Name the scope, intended users, and authoritative evidence sources.222. Extract terms as they are actually used. Preserve conflicting definitions and overloaded words.233. For each concept, record `Term`, `Proposed definition`, `Evidence`, `Examples`, `Non-examples`, `Relationships`, `Invariants`, `Authority`, and `Status`.244. Separate business concepts from storage names, API fields, UI labels, implementation classes, and vendor terminology.255. Identify synonyms, homonyms, missing concepts, ambiguous boundaries, and terms whose meaning changes by context.266. Test the model against representative scenarios and existing interfaces. Record contradictions rather than silently choosing a definition.277. Mark every entry as observed, proposed, ratified, rejected, or unresolved. Name the decision owner for ratification when known.2829## Boundaries3031- Do not rename code, schemas, or public interfaces without separate implementation authority.32- Do not declare a proposed definition canonical from repetition alone.33- Keep private product language in its owning repository or private overlay.3435## Output3637Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.3839Return the vocabulary table, relationship notes, contradictions, ratification needs, and migration implications.4041## Example4243Synthetic example; not an observed client result.4445Input: Sales uses account for a company; billing uses it for a payment ledger.4647Output: Define separate Company and Billing Account concepts, with an explicit relationship. These are proposed terms until the domain owners confirm them.