migration-utility

Use automatically before any completion, successful, passing, PR-ready, merged, or stage-complete statement to verify fresh evidence and choose accurate claim wording.

Use internally when /refactor-mart dispatches one approved Type: int or Type: mart candidate

Use when a monolith warehouse or lakehouse has a whole-warehouse `warehouse-ddl/` snapshot and needs tables or views grouped into business data domains with data owners for data mesh decentralization, setup-source selection, migration planning, or scope and migrate-mart inputs.

Use when generating or revising one dbt model for a single profiled table or view after refactor and approved test-spec work are complete.

Use when the generate-model workflow needs a read-only review of generated dbt model artifacts before accepting the result or sending it back for fixes.

Use internally when /refactor-mart dispatches one approved Type: stg candidate

Use when a migrated table, view, or materialized view needs a new or merge-safe `test-specs/<schema.object>.json`, especially after SQL changes or reviewer feedback.

Use when a selected mart unit must be analyzed into staging and higher-layer refactor candidates before any code changes

Use when the user asks to review, clear, suppress, or investigate /status catalog diagnostics for a single table or migration object.

Use when generated dbt unit test specs may have branch-coverage gaps, fixture-quality problems, or unresolved warnings across table, view, or materialized-view cases

Use when scoping a single table, view, or materialized view for migration and the next step depends on identifying its writer, SQL structure, or dependency call tree from catalog-backed DDL context.

Use when profiling a single table, view, or materialized view for migration and the next step depends on persisted classification, keying, watermark, foreign-key typing, PII handling, or stg-vs-mart view classification.

Use when stored procedure, view, or materialized-view SQL must be restructured into import/logical/final CTEs before proof-backed migration persistence.

Use when the user asks to "list tables", "list procedures", "show me object X", "what references Y", or wants to browse catalog contents.

Use when editing, generating, reviewing, or debugging migrated dbt unit test specs and review artifacts that must stay consistent across paired test skills.