modelgen-relationallisted

Extract module models from Agile user stories using Domain-Driven Design (DDD) principles. Produces ERD diagrams (Mermaid) and detailed model documentation per module. Use this skill whenever the user asks to extract a module model, data model, entity model, table design, schema design, or ERD from user stories. Also trigger when the user provides a set of user stories grouped by module and asks for entity/relationship analysis, database schema extraction, or DDD model generation. Even if the user says "analyze these stories" or "what entities do I need", this skill applies if the input contains structured Agile user stories with module groupings. Also trigger when the user says "update the model" or "upgrade the model" to incrementally evolve an existing module model based on changes in PRD.md. Accepts an application name (mandatory), version (mandatory), and optional module argument (e.g., `/modelgen-relational hub_middleware v1.0.3` or `/modelgen-relational hub_middleware v1.0.3 module:Location Information
rashidee/co2-skills · ★ 3 · AI & Automation · score 77

Install: claude install-skill rashidee/co2-skills

# Relational Model Generator Extract structured module models from Agile user stories following a systematic DDD methodology. ## When to Use Trigger this skill when the user asks to: - Extract a module model, data model, or entity model - Generate an ERD or entity-relationship diagram from user stories - Design database tables or schema from requirements - Perform DDD analysis on user stories - Update an existing module model based on story changes - Upgrade the model to a new version - Detect and fix outdated/invalid model elements ## Version Gate Before starting any work, resolve the application folder first (see Input Resolution below), then check `CHANGELOG.md` in the application folder (`<app_folder>/CHANGELOG.md`): 1. If `<app_folder>/CHANGELOG.md` does not exist, skip this check (first-ever execution for this application). 2. If `<app_folder>/CHANGELOG.md` exists, scan all `## vX.Y.Z` headings and determine the **highest version** using semantic versioning comparison. 3. Compare the requested version against the highest version: - If requested version **>=** highest version: proceed normally. - If requested version **<** highest version: **STOP immediately**. Print: `"Version {requested} is lower than the current application version {highest} recorded in <app_folder>/CHANGELOG.md. Execution rejected."` Do NOT proceed with any work. ## Input Resolution The skill requires mandatory `<application>` and `<version>` arguments, with an optional `module:` argume