Domain Skill — Ubiquitous Language for Human-AI Software Building
This is a library skill. It doesn't run standalone — it holds the shared
vocabulary that you, the agent, and other skills cite when describing work.
Why this exists
AgentOps's existing skills (research, plan, crank, validate, ...) are verbs.
This skill holds the nouns and the discipline they operate on. When a session
talks about "this is a tracer bullet" or "we need a vertical slice through the
eval surface," the meaning is fixed here, not improvised.
Status
Tracer bullet shape, not yet canonical. This skill currently holds:
- 6 structural primitives (Entry, Index, Citation, Primitive, Slice, Anti-Pattern)
- 1 test entry (Tracer Bullet) written using only citations to the 6 primitives
If the test entry can describe its own concept using only the primitives, the
shape works and we grow the corpus by adding more entries — never new
structural primitives without operator consent.
How to use this skill
- Read
references/INDEX.md first — it lists every entry by kind and status.
- Load only the entries relevant to the current work. Do not preload the
whole corpus — that defeats the JIT purpose.
- When applying an entry, cite it: include the entry slug in your output, plan,
commit message, or
bd issue body so future sessions can trace the
reasoning.
- When you find a concept missing or misnamed, add a draft entry under
references/ and update INDEX.md. Promotion from draft to canonical
requires operator approval.
Entries (tracer-bullet set)
Structural primitives (the architecture):
references/entry.md — Entry: the atomic concept doc
references/index-primitive.md — Index: the discovery surface (concept)
references/citation.md — Citation: how Entries reference each other and how agents claim use
Vocabulary nouns (the working units):
references/primitive.md — Primitive: atomic capability (skill, hook, CLI command, eval suite)
references/slice.md — Slice: vertical work unit cutting through multiple Primitives
references/anti-pattern.md — Anti-Pattern: documented mistake with cost when ignored
Test entry:
references/tracer-bullet.md — Tracer Bullet: described using only citations to the six primitives above
Catalog:
references/INDEX.md — full corpus index
What's NOT here
- Procedural how-tos (those live in other skills)
- Repo conventions (those live in
skills/standards/)
- Findings, learnings, patterns (those live in
.agents/)
- Product framing (lives in
PRODUCT.md)
See also
skills/standards/SKILL.md — repo coding standards (sibling library skill)
docs/architecture/primitive-chains.md — concrete AgentOps primitive layers
(Mission/Discovery/Risk/Execution/Validation/Learning/Ratchet/Continuity)
that compose the domain into chains
1---2name: domain-63description: Canonical vocabulary for human-AI software work.4---5# Domain Skill — Ubiquitous Language for Human-AI Software Building
6
7This is a **library skill**. It doesn't run standalone — it holds the shared
8vocabulary that you, the agent, and other skills cite when describing work.
9
10## Why this exists
11
12AgentOps's existing skills (research, plan, crank, validate, ...) are verbs.
13This skill holds the nouns and the discipline they operate on. When a session
14talks about "this is a tracer bullet" or "we need a vertical slice through the
15eval surface," the meaning is fixed here, not improvised.
16
17## Status
18
19**Tracer bullet shape, not yet canonical.** This skill currently holds:
20
21- 6 structural primitives (Entry, Index, Citation, Primitive, Slice, Anti-Pattern)
22- 1 test entry (Tracer Bullet) written using only citations to the 6 primitives
23
24If the test entry can describe its own concept using only the primitives, the
25shape works and we grow the corpus by adding more entries — never new
26structural primitives without operator consent.
27
28## How to use this skill
29
301. Read `references/INDEX.md` first — it lists every entry by kind and status.
312. Load only the entries relevant to the current work. Do not preload the
32 whole corpus — that defeats the JIT purpose.
333. When applying an entry, cite it: include the entry slug in your output, plan,
34 commit message, or `bd` issue body so future sessions can trace the
35 reasoning.
364. When you find a concept missing or misnamed, add a draft entry under
37 `references/` and update `INDEX.md`. Promotion from `draft` to `canonical`
38 requires operator approval.
39
40## Entries (tracer-bullet set)
41
42Structural primitives (the architecture):
43
44- [`references/entry.md`](references/entry.md) — Entry: the atomic concept doc
45- [`references/index-primitive.md`](references/index-primitive.md) — Index: the discovery surface (concept)
46- [`references/citation.md`](references/citation.md) — Citation: how Entries reference each other and how agents claim use
47
48Vocabulary nouns (the working units):
49
50- [`references/primitive.md`](references/primitive.md) — Primitive: atomic capability (skill, hook, CLI command, eval suite)
51- [`references/slice.md`](references/slice.md) — Slice: vertical work unit cutting through multiple Primitives
52- [`references/anti-pattern.md`](references/anti-pattern.md) — Anti-Pattern: documented mistake with cost when ignored
53
54Test entry:
55
56- [`references/tracer-bullet.md`](references/tracer-bullet.md) — Tracer Bullet: described using only citations to the six primitives above
57
58Catalog:
59
60- [`references/INDEX.md`](references/INDEX.md) — full corpus index
61
62## What's NOT here
63
64- Procedural how-tos (those live in other skills)
65- Repo conventions (those live in `skills/standards/`)
66- Findings, learnings, patterns (those live in `.agents/`)
67- Product framing (lives in `PRODUCT.md`)
68
69## See also
70
71- `skills/standards/SKILL.md` — repo coding standards (sibling library skill)
72- `docs/architecture/primitive-chains.md` — concrete AgentOps primitive layers
73 (Mission/Discovery/Risk/Execution/Validation/Learning/Ratchet/Continuity)
74 that compose the domain into chains