modelgen-relational

To generate an ER diagram from agile user stories, provide the module name, application name, and version. The skill applies Domain-Driven Design principles to extract structured models and outputs a Mermaid ERD with traceability to the source stories.

Yes, you can use Domain-Driven Design to create a relational model with version filtering. The skill processes stories grouped by module and version, enforcing per-module boundaries and filtering changes to support incremental model evolution.

Documenting bounded contexts and domain events is best handled by extracting structured module models from user stories. This produces a comprehensive domain model package including entity catalogs, enums, and domain events for stakeholder review.

Maintain traceability from agile stories to database design by generating artifacts like erd.mermaid and model.md. These files document the resulting relational model and explicitly link entities and attributes back to their source user stories.

Yes, this approach to relational model generation supports incremental changes across versions. It resolves versioned changes and NFR impacts to support incremental model evolution while maintaining strict per-module boundaries.

Converting user stories into a relational domain model produces erd.mermaid and model.md artifacts. These files contain the ERD diagrams, entity relationship catalogs, attribute details, and enums documenting the complete relational structure.