What problem does it solve? Brownfield database changes often fail because design decisions are made from incomplete DDL, ORM guesses, or invented naming conventions. This Skill produces an implementation-ready database design package where every table, column, stored procedure, migration, and naming decision traces back to current-state evidence or is explicitly marked unknown. ## Core Features & Use Cases - Evidence-Based Design: Builds logical and physical model changes strictly from current database state analysis and registered source-structure findings, with XDDP traceability rows linking requirement differences to each design item. - Naming and Convention Discipline: Derives table, column, stored procedure, and migration names from existing DB naming rules, table-definition local rules, and stored procedure analysis instead of preference. - Migration and Risk Planning: Produces migration, backfill, data correction, rollback, transaction, concurrency, and validation plans with explicit unknowns and handoff owners. - Use Case: When a requirement change adds a new entity to an existing SQL Server-backed application, use this Skill to design the schema change, name objects per existing conventions, plan the migration and backfill, and hand off a reviewable package before any code is written. ## Quick Start Ask the AI to design the database changes for an approved requirement using the registered current database state analysis and source-structure findings for the affected targets.
