All skills
data-migration-design
FoundationJIT onlyanalysis-agent/task-agent/review-agent: use when migration, backfill, deployment order, rollback, or live-data safety needs design; skip when no data migration exists.
- Group
- Data & API contracts
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- design schema migration data backfill rollback validation and deployment ordering
Do not use when
Anti-triggers — as binding as the triggers above
- no task-local data migration design decision is required
Required inputs
What must be supplied before this skill can decide anything
- current task contract
- selected primary Professional Skill
- task-local trigger evidence
Output contract
What this skill owes the next role
- migration decision with source and target state, compatibility sequence, writer and backfill coordination, resumability, validation evidence, rollback limits, completion condition, and residual owners
Escalation signals
When this skill must hand the decision back
- Unsafe migrations can lock tables lose data or block rollback
Loaded by
This skill never owns a task. These professionals may pull it in as Layer 3.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| benchmarks-and-patterns.mdbenchmark-pattern | Migration phases, backfill, cutover, or rollback tiers remain open. | No schema, data, or mixed-version transition changes. | AnalysisTaskReview |
| checklist.mddecision-checklist | Migration spans locks, checkpoints, dual operation, or irreversible cleanup. | An additive metadata change needs no data movement. | AnalysisTaskReview |
| evidence-patterns.mdevidence-pattern | Safety claims require fresh dry runs, counts, or restore rehearsal. | No migration-readiness claim is being closed. | AnalysisTaskReview |