Domain Entity Discovery

Goal

Before implementing domain entities, identify which ones are needed to correctly represent the business domain described in the task.

Domain entity discovery is the process of extracting domain concepts from requirements and determining which of those concepts should be modeled as domain entities. This step must happen before applying any implementation skill — aggregate boundaries, reference direction, optionality, typed IDs, immutability, repositories, and entry points all depend on knowing which entities exist and how they relate.

The agent must propose a domain model and validate it with the human before writing code. The agent should not guess or assume which entities the domain needs — it should reason from the requirements, propose explicitly, and wait for confirmation.

What Counts as In Scope

Apply this skill when the task does one or more of these things:

• requires modeling a new domain area that does not yet exist in the codebase
• introduces a new feature or flow that involves domain concepts not yet represented as entities
• extends an existing domain area with concepts that may require new entities
• asks the agent to implement something end-to-end where the domain model is not predefined