Domain Modeling

Build and sharpen the project’s domain model — challenge terminology, stress-test edge cases, and maintain the glossary and ADRs.

Description

The domain-modeling skill is the active discipline of changing the domain model: challenging terms that conflict with the glossary, proposing precise canonical terms for fuzzy language, stress-testing relationships with concrete scenarios, cross-referencing the user’s statements against the code, and recording resolved terms and decisions the moment they crystallise.

File locations:

• Glossary: resources/agent-docs/GLOSSARY.md

• ADRs: resources/agent-docs/adr/NNNN-slug.md

Files are created lazily, only when there is something to write. ADRs are offered only when a decision is hard to reverse, surprising without context, and the result of a real trade-off — all three.

Triggers

/wf:domain-modeling

Also: “pin down terminology”, “ubiquitous language”, “write an ADR”.

Output

Glossary entries (tight, opinionated definitions with _Avoid_ alternatives) and single-paragraph ADRs with sequential numbering.

Attribution

Adapted from the domain-modeling skill in mattpocock/skills (MIT license).