From virtual-team
Defines the domain glossary convention via a CONTEXT.md file to ensure consistent terminology across specs, plans, and code. Use when a project has or needs a shared vocabulary.
How this skill is triggered — by the user, by Claude, or both
Slash command
/virtual-team:domain-glossaryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
`CONTEXT.md` is an optional file at the repository root that defines the project's domain language. It gives the pipeline a shared vocabulary so specs, plans, and code use consistent terminology.
CONTEXT.md is an optional file at the repository root that defines the project's domain language. It gives the pipeline a shared vocabulary so specs, plans, and code use consistent terminology.
CONTEXT.md is optional. Commands work without it. When present, commands read it during context loading and prefer its defined terms over synonyms.
Create CONTEXT.md when:
start offers to scaffold it during repo initialization# Domain Context
## Language
| Term | Definition | Avoid |
|------|-----------|-------|
| [Term] | [What it means in this project] | [Synonyms to avoid] |
## Relationships
- A **[Term A]** contains one or more **[Term B]**
- A **[Term B]** references exactly one **[Term C]**
## Example Dialogue
> "When a customer places an **order**, the system creates **line items**..."
## Flagged Ambiguities
- "[Term]" — currently means both X and Y. Needs splitting when [condition].
Commands that read CONTEXT.md:
CONTEXT.md → commands proceed normally, no warningdocs/decisions/2026-04-29-domain-glossary-convention.mdstart scaffolds CONTEXT.md when the user opts in during repo initialization/virtual-team:grill command maintains CONTEXT.md inline during grilling sessionsnpx claudepluginhub ovargas/virtual-team --plugin virtual-teamEstablishes and maintains project domain language via a CONTEXT.md glossary, following ubiquitous language principles. Use when entering a new project, defining terms, or resolving ambiguous language during planning or debugging.
Extracts canonical domain terms into CONTEXT.md, flags ambiguities and synonyms. Use when authoring or updating CONTEXT.md or when a new domain term emerges.
Captures canonical definitions of domain terms in CONTEXT.md along with NOT-references to resolve ambiguity. Useful during interviews, spec reviews, or anytime a fuzzy word needs a single authoritative meaning before its sense drifts.