patterns-entity-modeling

To extract domain entities and attributes from user stories, provide your requirements to the Skill, which identifies domain entities, defines attribute schemas, and models relationship patterns using Domain-Driven Design principles to generate a formal data model.

Modeling entity relationships and cardinality involves transforming requirements into explicit entity definitions, which this process uses to document relationship patterns like 1:N and N:M alongside state machines to produce a reusable data-model.md file.

Yes, you can document state machines for stateful entities. The Skill extracts stateful entities from requirements and enforces explicit documentation formats to generate state machine documentation within the formal data model output.

Yes, this approach works for brownfield projects. It helps domain architects and engineers derive clean data models from ambiguous requirements by formalizing domain entities, attributes, and relationships across existing features.

The entity modeling process generates a structured data-model.md file. This output includes explicit entity definitions, attribute schemas, relationship patterns, and state machine documentation to guide implementation.