domain-modeling
Use when a project needs shared terminology, glossary updates, ADRs, clearer domain language, or when user language conflicts with existing code, ticket, board, project, workflow, or CONTEXT.md terms.
SKILL.mdskills/domain-modeling/SKILL.md
GitHubDomain Modeling
Use this to keep the project language sharp while planning or implementing.
Workflow
- Look for
CONTEXT.md,CONTEXT-MAP.md, and nearby ADRs. - When a term is fuzzy, propose one canonical term and test it with a concrete scenario.
- When user language conflicts with code or docs, surface the conflict and resolve it before implementation.
- Update the glossary only when a term is settled.
- Create an ADR only when the choice is hard to reverse, surprising without context, and the result of a real tradeoff.
DecisionsAI Fit
- Use board/ticket/workflow names as evidence, not as the glossary by themselves.
- Keep glossary entries free of implementation detail.
- Put implementation decisions in ADRs or workflow artifacts, not in
CONTEXT.md. - Prefer project memory sync when the active workflow needs the term later.