domain-modeling · Skill Details

Mechanism

When It Triggers · How It Works · What It Produces

Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.

Trigger: Invoked when the user wants to pin down domain terminology / ubiquitous language, record an architectural decision, or maintain the domain model. Other skills like /grill-with-docs, /triage, and /improve-codebase-architecture also call /domain-modeling during conversations to keep the domain model active.
Mechanism: Continuously performs five activities during a session — challenge existing terminology ("Your glossary defines 'cancellation' as X, but you seem to mean Y"), sharpen fuzzy language ("You said 'account' — do you mean Customer or User?"), stress-test with scenarios, cross-validate code against the model, and update CONTEXT.md inline. ADRs are created only when all three conditions are met: hard to reverse, surprising without context, and the result of a real trade-off.
Output: A continuously updated CONTEXT.md (pure glossary, no implementation details), plus optional ADRs documenting decisions future readers would question. Artifacts persist in the project filesystem, supporting multi-context projects via CONTEXT-MAP.md.

Use Cases

Two Typical Use Cases

Scenario 01

Establishing a shared domain language in a new project

Early in a project, team members use terms like "user", "customer", and "account" interchangeably, causing communication ambiguity. After invoking `/domain-modeling`, the agent detects term conflicts in real time during each conversation, clarifies vague "account" into distinct concepts like "Customer" or "User", and automatically updates CONTEXT.md. When the team makes a hard-to-reverse design decision (e.g., choosing event sourcing), the skill suggests creating an ADR documenting the context and alternatives.

Scenario 02

Detecting code-vs-terminology inconsistency during refactoring

During payment module refactoring, a developer finds the "cancel" operation in code actually does a "partial refund," not a full cancellation. Invoking `/domain-modeling` has the agent cross-check code against CONTEXT.md, surfacing the inconsistency immediately. When the developer confirms the correction, the skill updates both the glossary and code logic, keeping domain language and implementation aligned.

Skill Relationships

Which Skills I Use · Which Skills Use Me

Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.

Tier 1 · These Skills Use Me

Tier 2 · Current Skill

domain-modelingWorkflow

Tier 3 · I Use These Skills

No explicit dependency on other Skills

Full Relationship Graph

Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.

Skill File

SKILL.md

Open in GitHub ↗

SKILL.mdLoading from GitHub…

Skill Composition

Open in GitHub ↗

SKILL.md25.0%
other75.0%

▸skills/domain-modeling/
▸domain-modeling
- ·ADR-FORMAT.md
- ·CONTEXT-FORMAT.md
- ·SKILL.md
- ▸agents
  - ·openai.yaml

Per the Agent Skills spec, SKILL.md is the only required file. The colored bars classify the rest into the three spec-aligned optional directories (scripts / references / assets) and an 'other' bucket. The full directory tree is below.

Related in Skillset

You May Also Need These Skills

ask-matt

A router skill for the entire skillset: when the user can't remember which skill to use or which flow fits their situation, they invoke this to get a recommendation. It describes the main "idea → ship" flow (grill-with-docs → to-spec/to-tickets → implement), plus on-ramps (triage, diagnosing-bugs, wayfinder), codebase health (improve-codebase-architecture), vocabulary layers (domain-modeling, codebase-design), and standalone skills (grill-me, prototype, research, teach). Following its map leads users to the correct workflow entry point.

Workflow

code-review

A two-axis code review skill: reviews a diff (from a fixed point to HEAD) along both Standards (coding standards + Fowler smell baseline) and Spec (faithful implementation of the originating issue/PRD). Both axes run as parallel sub-agents to avoid context pollution. The report aggregates findings without merging conclusions, ensuring "passes standards but implements the wrong thing" and "implements the right thing but breaks conventions" are both surfaced independently.

Workflow

codebase-design

A shared vocabulary skill for deep module design: provides a precise set of design terms (Module, Interface, Depth, Seam, Adapter, Leverage, Locality) guiding agents and developers to design "deep modules" — a lot of behaviour behind a small interface. Includes design principles (the deletion test, the interface is the test surface) and testability guidelines. A reference skill consumed by other skills (e.g., improve-codebase-architecture, tdd) and invoked directly by engineers.

Style Guide

diagnosing-bugs

A disciplined diagnosis loop for hard bugs and performance regressions. The core idea is to first build a tight feedback loop — no hypothesis phase without one. Six phases: build feedback loop → reproduce + minimise → generate 3-5 falsifiable hypotheses → instrument by prediction → fix + regression test → cleanup + post-mortem. If the codebase architecture can't lock down the bug, it recommends handing off to the improve-codebase-architecture skill.

Workflow