mcpField
D
domain-modeling

domain-modeling

github.com/idaibinDevelopment642 installsUpdated 1d ago
Repository

About domain-modeling

A skill for resolving shared domain language, rules, and context boundaries across teams or lifecycle stages. It distinguishes sourced facts from assumptions and routes feature-specific behavior to product-spec.

Key features

  1. 01Identify conflicting shared terms and rules
  2. 02Track fact sources and evidence
  3. 03Separate facts, assumptions, and unknowns
  4. 04Map affected owners and handoffs

Use cases

  1. 01Resolve terminology conflicts across teams
  2. 02Clarify lifecycle and context boundaries

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/idaibin/skills --skill domain-modeling

After installing, type/domain-modelingin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
references/
eval-cases.md
modeling-guide.md
usage.md

Details

From the project README

Domain Modeling

Entry Gate

Resolve cross-functional language and rules only when the ambiguity spans owners or lifecycle boundaries. Require an identified fact source and scope; do not invent product decisions or technical design.

Route Map

Request conditionReadResult
Shared terms, invariants, or context boundaries conflictmodeling guideNamed glossary/context/rule facts
A feature-local behavior or acceptance is unresolvedusageRoute to product-spec
Need examples and nearest boundariesusageOwner decision

Invariants

  • Keep facts, assumptions, unresolved questions, and implementation choices distinct.
  • Preserve the source authority and evidence level for each conclusion.
  • Do not write a competing product/UI/design contract, source change, review, or Git result.

Output Map

Return the named fact source, terms/rules/context boundaries, source basis, unresolved ambiguities, affected owners, and next semantic handoff.

Reference Map

  • Read modeling guide for context, lifecycle, rule, and validation procedures.
  • Read usage for mode selection and boundaries.
  • Maintainers only: read eval cases; do not load it during ordinary runtime.

Comments

Markdown supported