Database Design Quality Review

Review ERDs, DDL, ORM schemas, data ownership, lifecycle, query constraints, transaction/concurrency, migration compatibility, and recovery design before implementation or migration. It produces DB-## findings and validation preparation; it does not connect to a real database or approve launch.

When to Use

• Use it to check model integrity, constraints, indexes, lifecycle/privacy, and data ownership.
• Use it to identify transaction, concurrency, migration rollback, backup/recovery, and performance risks.
• Use it when DDL or migration material is incomplete but a bounded design review is needed.

Do not use it to execute migrations, connect to production, benchmark queries, or infer business rules from table names.

Output Format Options

• Use Markdown by default; when a table, CSV, or JSON is requested, preserve the same evidence, status, impact, owner, and validation fields.
• Do not present a structured format or static inventory as execution, pass, approval, or release evidence.

How to Use