What problem does it solve? A PRD describes product behavior, not tables, so data modeling decisions often get made implicitly by whoever writes the first migration. This Skill turns an approved PRD into an explicit, reviewed database schema document before any implementation begins. ## Core Features & Use Cases - Entity Derivation: Extracts entities from PRD user stories and objectives, ensuring every table traces to actual product behavior rather than guesswork. - Full Schema Design: Defines columns with engine-specific types, relationships with cardinality and on-delete behavior, indexes tied to named queries, and enforceable constraints. - User Review Gate: Presents the model for explicit approval before writing anything, then saves the result to docs/schema/<name>.md as Markdown, not SQL DDL. - Use Case: You have an approved PRD for an experiment-tracking feature and need the data model designed and documented before breaking the work into implementation tasks. ## Quick Start Use the get-schema skill to design the database schema from the PRD at docs/prd/experiment-tracker.md and write it to docs/schema/.
