pm-entity-registry

Extracting business entities from a PRD involves identifying real domain objects within Business Capabilities and distinguishing them from technical components. This process structures vague capabilities into clear domain models to prevent inconsistent implementation decisions.

Defining lifecycle states and transitions requires modeling state machines using Mermaid syntax to map business rules. This approach clarifies architectural boundaries by detailing how business objects evolve and what events they emit during each state change.

Generating an entity registry for FDD workflows produces a maintained domain/entities.md artifact from product requirements. This register supports feature planning and engineering implementation by aligning architectural definitions with extracted domain objects.

Yes, you can use Mermaid state machines for PRD analysis to achieve architectural alignment. Modeling state transitions visually defines business lifecycle states and emitted events, ensuring engineering teams implement consistent domain logic based on structured requirements.

Domain modeling for product architecture requires separating real business objects from technical components to ensure accurate entity extraction. Distinguishing these elements prevents unclear domain models and missing lifecycle rules during the transition from PRD capabilities to development.

You should not use an entity registry for product development when a PRD lacks defined Business Capabilities or when the project does not require structured domain modeling. It is specifically designed for scenarios needing FDD workflows and lifecycle transition mapping.