Orchestrate database migration and data-risk work with consistent safety checks — combines data integrity, migration, and deployment verification agents
From clavainnpx claudepluginhub mistakeknot/interagency-marketplace --plugin clavain[migration file, PR number, or description of data change]Runs 3 specialized agents in parallel to produce a comprehensive safety assessment for DB/data-risk work.
<migration_context> #$ARGUMENTS </migration_context>
If empty: Ask: "What data change are you making? Include migration files, affected tables/columns, and whether this touches production data."
Read migration files. Identify: affected tables/columns, schema change vs backfill vs both, production data at risk, reversibility.
Task(data-migration-expert): "Review for safety: <context>. Check: ID mapping correctness, swapped values, orphaned associations, dual-write patterns. Produce validation queries."
Task(interflux:review:fd-correctness): "Review for integrity: <context>. Check: referential integrity, transaction boundaries, privacy compliance, constraint violations. Identify invariants."
Task(interflux:review:fd-safety): "Create Go/No-Go checklist for: <context>. Include: pre-deploy verification queries, post-deploy checks, rollback procedure, monitoring plan."
## Migration Safety Assessment
### Summary
- **Migration:** [description]
- **Risk Level:** LOW / MEDIUM / HIGH / CRITICAL
- **Reversible:** yes / no / partial
### Data Migration Expert Findings
### Data Integrity Review
### Deployment Checklist
#### Pre-Deploy
- [ ] [verification query]
- [ ] [backup/snapshot taken]
#### Deploy
- [ ] [migration command + monitoring check]
#### Post-Deploy
- [ ] [verification query + data count comparison]
#### Rollback
- [ ] [rollback steps]
### Go/No-Go Decision
- NO-GO if: [blocking conditions]
- GO if: [all pre-deploy checks pass]
Risk level: [HIGH/MEDIUM/LOW]
1. Proceed (all checks pass)
2. Fix issues first (P1 findings)
3. Review full report
git revert.