domain
GitHub当需要精确理解 AgentOps 术语或边界上下文含义时加载。通过查阅契约文件返回精确定义和来源，防止同义词混淆，确保语义一致性。
Trigger Scenarios
Install
npx skills add boshu2/agentops --skill domain -g -y
SKILL.md
Frontmatter
{
"name": "domain",
"context": {
"intent": {
"mode": "none"
},
"window": "isolated",
"intel_scope": "none"
},
"consumes": [],
"metadata": {
"tier": "knowledge",
"effects": [],
"disposition": "keep_specialist",
"capabilities": [
"domain"
],
"dependencies": [],
"canonical_status": "canonical"
},
"produces": [
"stdout"
],
"practices": [
"ddd-bounded-context",
"pragmatic-programmer"
],
"context_rel": [],
"description": "Load the AgentOps language and bounded-context contracts when a term needs precise meaning. Triggers: \"define this domain term\", \"check the bounded context\".",
"hexagonal_role": "domain",
"output_contract": "concise domain-language reference",
"skill_api_version": 1
}
Domain — ubiquitous language
Use this read-only library when an AgentOps term or bounded-context boundary needs precise meaning.
Returning the exact contract definition works because two contexts that read the same source line cannot drift apart on a term; a paraphrase reintroduces the ambiguity the lookup exists to remove.
Named failure mode — synonym smuggling: answering with a near-synonym ("close" for "verdict") that quietly imports lifecycle authority the term does not carry.
Anti-pattern: defining a term from memory because the contract file is one read away. Corrective: always cite the definition and its source path from the live contract, even for terms you are sure about.
Procedure
- Read
docs/contracts/ubiquitous-language.mdfor the term. - Read
docs/contracts/bounded-contexts.yamlonly when ownership or a port boundary matters. - Return the exact definition and source path.
- Stop.
Do not invent synonyms that imply lifecycle authority. In particular, Plan, Candidate, manifest, verdict, revision, strategy, and adapter are semantic terms; queue, claim, lease, close, land, release, and delivery belong to caller systems rather than AgentOps core state.
The product-architecture terms — operations layer, federated integration graph, semantic work-and-proof protocol, RPI traversal — and their forbidden conflations live in the same contract. The traversal is RPI; the graph is the topology; the protocol defines interoperability; the operations layer is the product. None of the four is "a loop".
Vocabulary changes are normal source edits to the two contracts above. This skill does not promote terms, mutate a knowledge index, or create continuation.
Version History
-
7b07a7d
Current 2026-08-19 21:59
对齐 AgentOps 为代理工程的操作层身份，新增关于操作层、集成图、协议及 RPI 遍历的术语定义与禁止混淆说明。
- 3f402e5 2026-07-24 22:07
