data-model-discovery

Gathers and validates data model requirements through structured discovery questions before schema design.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/snoodleboot-io/discrecontinual_equations --skill data-model-discovery-snoodleboot-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: data-model-discovery
Source: https://github.com/snoodleboot-io/discrecontinual_equations/tree/main/.claude/skills/data-model-discovery
Command: npx skills add https://github.com/snoodleboot-io/discrecontinual_equations --skill data-model-discovery-snoodleboot-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing a data model without understanding requirements leads to costly redesigns, slow queries, and missing lifecycle policies. This Skill provides a systematic discovery process that captures entities, relationships, query patterns, write volumes, and scale constraints before any schema is written. ## Core Features & Use Cases - Discovery Question Framework: Structured questions covering core entities, read patterns, write patterns, data lifecycle, and scale constraints with follow-up prompts and example answers. - Entity & Relationship Techniques: Noun extraction, use case walkthroughs, event storming, cardinality analysis, and dependency analysis to identify entities and map relationships. - Validation Strategies: Query walkthroughs, normalization checks (1NF-3NF with strategic denormalization), write path testing, and scalability analysis to verify the model against real use cases. - Use Case: Before building an e-commerce backend, walk through the discovery framework to document that orders need 5000 status updates per day, users require soft-delete with 7-year retention, and the orders table will reach 10M rows in two years, then produce a discovery summary that drives ERD and schema design. ## Quick Start Ask me the data model discovery questions for my application so we can document entities, relationships, query patterns, and scale requirements before designing the schema.

Frequently Asked Questions about data-model-discovery

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

FAQPage Schema
How do I gather requirements before designing a database schema?▼

Use a structured discovery process covering five areas: core entities and relationships, read patterns, write patterns, data lifecycle, and scale constraints. Document answers with frequency and volume estimates, then validate the model against real query walkthroughs before writing any DDL.

What questions should I ask before creating a data model?▼

Ask about core entities and their cardinality, the most frequent read and write operations with volume estimates, soft-delete and audit trail requirements, expected record counts and growth, and performance SLAs. Follow up on transactional boundaries and concurrency risks like stock update race conditions.

How do I identify entities and relationships in requirements?▼

Apply noun extraction to requirements documents, walk through user journeys to map CRUD operations per step, or use event storming to list domain events and the entities they create or modify. Determine cardinality by asking how many of each entity the other can have.

When should I denormalize a database schema?▼

Denormalize strategically when read performance is critical and joins are too expensive, such as storing user_email on orders to avoid a join on every list query. Always document the decision with the measured benefit and target third normal form by default.

What are common data modeling mistakes to avoid?▼

Common mistakes include jumping to schema before discovery, ignoring query patterns, under-specifying relationships, forgetting data lifecycle policies like soft-delete and retention, and ignoring scale so queries that work at 10K rows fail at 1M rows.