conceptual-modeling

Build implementation-neutral domain models from stakeholder requirements with entities and relationships.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/jacob-balslev/skill-graph --skill conceptual-modeling
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conceptual-modeling
Source: https://github.com/jacob-balslev/skill-graph/tree/main/marketplace/skills/conceptual-modeling
Command: npx skills add https://github.com/jacob-balslev/skill-graph --skill conceptual-modeling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conceptual modeling translates messy business requirements and stakeholder language into an implementation-neutral domain model that people can validate before design decisions lock in.

Core Features & Use Cases

  • Entity discovery & identity criteria: define distinguishable domain concepts and how to decide when two instances are the same.
  • Attribute placement & reification: decide what belongs on which entity, identify derived values, and promote relationship data into explicit entities when needed.
  • Named relationships with cardinality/optionality: model associations, aggregation/composition, and generalization/specialization with stakeholder-readable meaning.
  • Abstraction-level control & anti-pattern detection: prevent implementation leakage (tables/columns/UUIDs/DDL/OWL/DDD tactics) and catch common modeling failures (missing entities, god entities, phantom/unnamed relationships, over-formalization).
  • Stakeholder validation & scenario testing: verify the model with walkthroughs, negative tests, and conflict interviews.

Quick Start

Use conceptual-modeling when you need to produce a stakeholder-readable entity/relationship model for a new or changing domain while keeping it above logical/physical database, API, ontology, and DDD tactical design.

Frequently Asked Questions about conceptual-modeling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a domain model from messy stakeholder requirements?▼

To define entity identity criteria in domain modeling, you establish distinguishable domain concepts and rules for deciding when two instances represent the same thing. This prevents ambiguity and ensures consistent entity tracking before committing to implementation schemas or DDD tactical patterns.

How do I prevent implementation leakage in conceptual modeling?▼

Detecting domain modeling anti-patterns involves checking for missing entities, god entities, and phantom or unnamed relationships during the conceptual modeling process. Catching these common failures early ensures the model remains structurally sound and semantically accurate for stakeholder validation.

Can I use conceptual modeling for domain refactoring before API design?▼

Yes, conceptual modeling applies to domain refactoring and conflict resolution between stakeholders before API design. It produces an implementation-neutral entity-relationship model that validates business logic through walkthroughs and negative tests, ensuring correctness prior to schema or ontology commitments.

What is the best way to validate a domain model with stakeholders?▼

Relationship cardinality and optionality define the associations, aggregation, and generalization between entities using stakeholder-readable meaning. Modeling these relationships explicitly ensures the domain model accurately captures business rules without relying on physical database constraints or implementation tactics.