Domain
This skill makes a run cite where the project defines a term or convention
before using, renaming or applying it, and keep one meaning per bounded
context. A user sees it worked when each contested term comes back with its
source path, its context and a concrete example that tells the meanings apart.
Two independent uses: vocabulary work makes a term, name or
rule boundary precise enough for acceptance examples, code and conversation; a
conventions lookup finds the standard the repository
itself sets for a change. Neither needs the other. Plan
owns unified discovery and resumption; Domain resolves only the needed
vocabulary or rule boundary and returns it to the existing intent.
Vocabulary work
- Cite the existing owner. Find the vocabulary owner in the caller's
instructions, domain docs or contracts and read only the relevant terms. A
lookup is read-only. With no owner, label each definition as observed in
code or proposed.
- Keep one meaning per bounded context, the area where a term has one
agreed meaning and an owner for its rules. When a word crosses contexts,
name each meaning and the translation at the boundary instead of imposing
one global definition.
- Report code that disagrees with intent. Identify the actor, state,
operation and observable result the term denotes, then compare the intended
meaning with callers, types and tests. A mismatch is a finding to resolve:
renaming code does not add missing behavior, and redefining the term to
match the code hides the defect.
- Price renames of shared names. Exported names, serialized fields, stored
values and API payloads need compatibility work (migration, versioning,
client updates), not a cosmetic replacement. Keep naming changes within
authorized scope.
- Distinguish with an example. Separate competing meanings with a concrete
case; express a branching boundary as Given/When/Then and reuse it in
implementation and validation. Use the settled term in scenario names,
operations, types and documentation. Ask only when an unresolved
distinction would change behavior or ownership; a lookup needs no interview.
- Update the owner; add no glossary by default. When refinement is
authorized, update the existing owner with the meaning, context and example.
Without an owner, return the proposal in the caller's intent or conversation
rather than creating a new glossary file. Admit a term only when a newcomer
needs it and it is a concept of its own, not a property of another entry or
a general programming word. An entry gives one sentence of meaning plus any
lifecycle or ownership rules, defines the project terms it uses, and records
behavior, not current values, dates, owners or status. Keep another
context's alias as a translation; mark a retired synonym on the surviving
entry as a word to avoid.
- Propose a decision record only when it earns one. When a boundary or
rename becomes a design decision, propose an ADR only if it is costly to
reverse, would puzzle a later reader without its context, and chose between
real alternatives for stated reasons; otherwise the owner update and its
example are enough. Use the repository's decision-record format, or a short
title and one to three sentences of context, choice and reason. Keep
implementation detail out of the vocabulary owner.
Return vocabulary work in this shape. Stop when every contested term has a row
with a source and a distinguishing example, or an open question for the caller:
| Term |
Context |
Meaning |
Source |
Distinguishing example |
Open question |
|
|
|
<path:line, observed in code, or proposed> |
<Given/When/Then or concrete case> |
<caller decision, or none> |
After the table, list the translations between contexts, each located
code-versus-intent disagreement, the compatibility cost of any proposed rename,
and the owner updated or the text proposed for it. See
caller vocabulary examples.
The synonym smuggling failure substitutes a word that changes a term's
authority: calling a verdict a closure quietly assigns a tracker transition to
judgment. Keep the original term when a substitute would move responsibility.
AgentOps terms
Only when AgentOps itself is the subject, load its owners from
AgentOps terms. Do not apply AgentOps
vocabulary to an unrelated caller domain.
Conventions lookup
The standard for a change is the one the repository sets. Find its owners for
the touched paths: instruction files (AGENTS.md, CLAUDE.md, path-scoped
rules), formatter, linter and type-checker configuration, the CI workflow that
gates the change, and the existing code and tests in the same package. Cite
each convention by path. Configuration and CI that run outrank prose; where
two owners disagree, report the conflict rather than pick one. When the
repository states nothing for a question, say so and follow the surrounding
code; do not present a general language guide as the project's rule. A lookup
is read-only and creates no second approval or validation lane. It is done
when each convention question for the touched paths has a cited owner or the
answer "not stated".
Idea provenance: Matt Pocock's engineering skills (domain modeling), adapted for AgentOps.
1---2name: domain3description: 'Settle what domain terms mean per context, and which repository conventions or language standards (Go, Python) apply. Use when: names disagree or a rename is proposed.'4practices:5- ddd-bounded-context6- pragmatic-programmer7hexagonal_role: domain8consumes: []9produces:10- domain-language-guidance11context_rel: []12skill_api_version: 113user-invocable: true14metadata:15 source: https://skillmd.com/skills/hashgraph-online/domain16 capabilities: [domain, clarify_domain_language, reconcile_domain_names]17 effects: [update_existing_domain_contracts]18 canonical_status: canonical19 disposition: keep_specialist20 tier: knowledge21 dependencies: []22output_contract: cited domain definitions, concrete behavioral distinctions, and authorized updates to the existing vocabulary owner23---2425# Domain2627This skill makes a run cite where the project defines a term or convention28before using, renaming or applying it, and keep one meaning per bounded29context. A user sees it worked when each contested term comes back with its30source path, its context and a concrete example that tells the meanings apart.3132Two independent uses: [vocabulary work](#vocabulary-work) makes a term, name or33rule boundary precise enough for acceptance examples, code and conversation; a34[conventions lookup](#conventions-lookup) finds the standard the repository35itself sets for a change. Neither needs the other. [Plan](../plan/SKILL.md)36owns unified discovery and resumption; Domain resolves only the needed37vocabulary or rule boundary and returns it to the existing intent.3839## Vocabulary work40411. **Cite the existing owner.** Find the vocabulary owner in the caller's42 instructions, domain docs or contracts and read only the relevant terms. A43 lookup is read-only. With no owner, label each definition as observed in44 code or proposed.452. **Keep one meaning per bounded context**, the area where a term has one46 agreed meaning and an owner for its rules. When a word crosses contexts,47 name each meaning and the translation at the boundary instead of imposing48 one global definition.493. **Report code that disagrees with intent.** Identify the actor, state,50 operation and observable result the term denotes, then compare the intended51 meaning with callers, types and tests. A mismatch is a finding to resolve:52 renaming code does not add missing behavior, and redefining the term to53 match the code hides the defect.544. **Price renames of shared names.** Exported names, serialized fields, stored55 values and API payloads need compatibility work (migration, versioning,56 client updates), not a cosmetic replacement. Keep naming changes within57 authorized scope.585. **Distinguish with an example.** Separate competing meanings with a concrete59 case; express a branching boundary as Given/When/Then and reuse it in60 implementation and validation. Use the settled term in scenario names,61 operations, types and documentation. Ask only when an unresolved62 distinction would change behavior or ownership; a lookup needs no interview.636. **Update the owner; add no glossary by default.** When refinement is64 authorized, update the existing owner with the meaning, context and example.65 Without an owner, return the proposal in the caller's intent or conversation66 rather than creating a new glossary file. Admit a term only when a newcomer67 needs it and it is a concept of its own, not a property of another entry or68 a general programming word. An entry gives one sentence of meaning plus any69 lifecycle or ownership rules, defines the project terms it uses, and records70 behavior, not current values, dates, owners or status. Keep another71 context's alias as a translation; mark a retired synonym on the surviving72 entry as a word to avoid.737. **Propose a decision record only when it earns one.** When a boundary or74 rename becomes a design decision, propose an ADR only if it is costly to75 reverse, would puzzle a later reader without its context, and chose between76 real alternatives for stated reasons; otherwise the owner update and its77 example are enough. Use the repository's decision-record format, or a short78 title and one to three sentences of context, choice and reason. Keep79 implementation detail out of the vocabulary owner.8081Return vocabulary work in this shape. Stop when every contested term has a row82with a source and a distinguishing example, or an open question for the caller:8384| Term | Context | Meaning | Source | Distinguishing example | Open question |85|---|---|---|---|---|---|86| <term> | <bounded context> | <definition> | <path:line, observed in code, or proposed> | <Given/When/Then or concrete case> | <caller decision, or none> |8788After the table, list the translations between contexts, each located89code-versus-intent disagreement, the compatibility cost of any proposed rename,90and the owner updated or the text proposed for it. See91[caller vocabulary examples](references/caller-vocabulary.md).9293The **synonym smuggling** failure substitutes a word that changes a term's94authority: calling a verdict a closure quietly assigns a tracker transition to95judgment. Keep the original term when a substitute would move responsibility.9697### AgentOps terms9899Only when AgentOps itself is the subject, load its owners from100[AgentOps terms](references/agentops-terms.md). Do not apply AgentOps101vocabulary to an unrelated caller domain.102103## Conventions lookup104105The standard for a change is the one the repository sets. Find its owners for106the touched paths: instruction files (`AGENTS.md`, `CLAUDE.md`, path-scoped107rules), formatter, linter and type-checker configuration, the CI workflow that108gates the change, and the existing code and tests in the same package. Cite109each convention by path. Configuration and CI that run outrank prose; where110two owners disagree, report the conflict rather than pick one. When the111repository states nothing for a question, say so and follow the surrounding112code; do not present a general language guide as the project's rule. A lookup113is read-only and creates no second approval or validation lane. It is done114when each convention question for the touched paths has a cited owner or the115answer "not stated".116117Idea provenance: [Matt Pocock's engineering skills](https://github.com/mattpocock/skills) (domain modeling), adapted for AgentOps.