Data Modeling

Generate ERDs and data dictionaries documenting data structures and business rules.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Danhvb/my-ba-skills --skill data-modeling-danhvb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Data Modeling
Source: https://github.com/Danhvb/my-ba-skills/tree/main/multi-agent-ba/.agent/skills/senior-ba/data-modeling
Command: npx skills add https://github.com/Danhvb/my-ba-skills --skill data-modeling-danhvb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design data models, ERDs, and data dictionaries to document data structures, relationships, and business rules for system design and development.

Core Features & Use Cases

  • ERD creation: Generate clear entity-relationship diagrams for databases and applications.
  • Data dictionary templates: Produce standardized data dictionaries with field definitions, data types, and constraints.
  • Use Case: Document data requirements for new projects and align data models with business rules.

Quick Start

Create an ERD and data dictionary for the current project schema and output them to a single consolidated report.

Frequently Asked Questions about Data Modeling

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

FAQPage Schema
How do I create an ERD for a new database schema?

You create an ERD by defining entity-relationship diagrams to document data structures and relationships for system design. This process aligns data requirements with business rules to guide your database design.

What is the best way to generate a standardized data dictionary?

The best way to generate a data dictionary is producing standardized templates that capture field definitions, data types, and constraints. This documents your existing schemas and aligns data models with business rules.

How does database normalization guidance work when documenting schemas?

Database normalization guidance works by applying functional rules to validate your schema during data modeling. It ensures documented data structures and relationships satisfy business requirements without redundancy.

Can I document data requirements for existing projects using this approach?

Yes, you can document data requirements for existing projects by mapping current schemas to standardized data dictionaries. This aligns your documented data structures and relationships with established business rules.

Do I need requirements analysis before designing data models?

You need requirements analysis before data modeling to align data structures with business rules. Analyzing requirements first ensures your ERD creation and schema validation satisfy the functional needs of your database design.