modelgen-relational

Name: modelgen-relational
Availability: InStock
Author: rashidee

Extract structured module models from Agile user stories into ERDs and documentation.

3|Updated Mar 15, 2026

Search Tags:#ddd #traceability #bounded-context #model-generation #er-diagram #relational-model #agile-stories

Ready to run

npx skills add https://github.com/rashidee/co2-skills --skill modelgen-relational

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: modelgen-relational
Source: https://github.com/rashidee/co2-skills/tree/main/skills/modelgen-relational
Command: npx skills add https://github.com/rashidee/co2-skills --skill modelgen-relational

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract structured module models from Agile user stories using Domain-Driven Design (DDD) principles to produce ERD diagrams (Mermaid) and detailed module documentation per module. This skill enables teams to translate requirements into a coherent relational model, ensuring traceability from stories to database design and governance artifacts.

Core Features & Use Cases

Extract structured module models from Agile user stories following a systematic DDD methodology and generate ERDs and module documentation.
Resolve module boundaries, versioned changes, and NFR impacts to support incremental model evolution.
Produce a comprehensive domain model package per module, including entity catalogs, attribute details, relationship catalogs, enums, and domain events for stakeholder review.

Quick Start

Provide the module name, application name, and version to generate the relational model artifacts.

Frequently Asked Questions about modelgen-relational

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate an ER diagram from agile user stories?▼

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.

Can I use Domain-Driven Design to create a relational model with version filtering?▼

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.

What is the best way to document bounded contexts and domain events from requirements?▼

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.

How to maintain traceability from agile stories to database design artifacts?▼

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.

Does this approach to relational model generation support incremental changes across versions?▼

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.

What artifacts are produced when converting user stories into a relational domain model?▼

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.