Domain Model Skill

Goal

Produce a clear domain model that captures the business concepts and their relationships. This model is the shared language between stakeholders and developers — it drives naming, component boundaries, and data design. Technology-agnostic: no database tables, no class syntax, no framework artifacts.

When to Use

• Scenario 1 (New product): Before designing architecture. "What are the core business concepts?"
• Scenario 2 (Existing system review): "Does the current system model correctly reflect the domain?"
• Before splitting a monolith: Identify bounded context boundaries.
• When teams disagree on terminology: Model the language explicitly.