SkillVaultskills Browse all 1,000+ skills

Testing · Version 1.0.0 · Reviewed 2026-08-02

Migration Parity Validator

Design confidence for dual-run parity design and behavioral equivalence testing with evidence, explicit trade-offs, and a verification plan.

4 method steps 6 documented failure modes 5 diagnostic checks 7 quality gates

Proves old and new implementations agree at the real integration boundary before a migration removes the fallback. It grounds the decision in paired outputs, routing, types, dimensions, timing, failure behavior, representative traffic, and tolerance rules and explicitly prevents unit tests passing while the new path drops, renames, reroutes, or aggregates data differently in production.

₹299 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools.

What this skill helps you do

  • Dual-run parity design
  • Behavioral equivalence testing
  • Migration divergence analysis

How Migration Parity Validator works

You provide

Current state, consumer inventory, and target state

It inspects

Coexistence and rollback viability for dual-run parity design

It decides

A behavioral equivalence testing sequence in reversible increments

You verify

Shadow comparison reports divergence rather than assuming zero

What it checks first

Migration Parity Validator proves old and new implementations agree at the real integration boundary before a migration removes the fallback. It grounds the decision in paired outputs, routing, types, dimensions, timing, failure behavior, representative traffic, and tolerance rules and explicitly prevents unit tests passing while the new path drops, renames, reroutes, or aggregates data differently in production. Use it when the work involves Dual-run parity design, Behavioral equivalence testing, Migration divergence analysis.

  1. Whether the old and new paths can coexist, which determines if incremental migration is possible at all.
  2. The true consumer inventory, including internal jobs, scripts, and integrations not visible in the main codebase.
  3. Data volume and the time the migration takes at production scale, not sample scale.
  4. Whether the change is backward compatible for data written by the previous version during rollout.
  5. The rollback path, and specifically whether it remains available after the first irreversible step.

Failure modes it recognizes

  • A migration validated on a sample that takes hours on production volume and holds a lock throughout.
  • Dual-write divergence where one write succeeds and the other fails, with no reconciliation.
  • A backfill that races with live writes and overwrites newer values with older ones.
  • Removing the old path before all consumers migrated, discovered by a quarterly batch job weeks later.
  • A schema change that is forward compatible but not backward compatible, blocking rollback.
  • Enum or type widening that older readers cannot parse, breaking during a partial rollout.

Answers it will reject

  • A big-bang cutover with a maintenance window, which concentrates all risk into one unrehearsed moment.
  • Migrating and refactoring simultaneously, which makes failures impossible to attribute.
  • Treating the migration as done at cutover rather than after the old path is removed and verified unused.
  • Skipping the shadow-read comparison because the new implementation "obviously" matches.

Decision rules it applies

  • Use expand-migrate-contract: add the new shape, write both, migrate readers, then remove the old shape.
  • Every increment must be independently verifiable and independently revertible.
  • Keep the old path observable until traffic proves equivalence; remove it only on evidence of zero use.
  • Prefer additive schema changes; a removal is a separate, later, deliberately scheduled change.

Evidence it asks for

  • Run shadow reads comparing old and new outputs, and report the divergence rate rather than assuming zero.
  • Instrument usage of the deprecated path with a caller identifier so removal can be proven safe.
  • Rehearse the migration on a production-sized copy and record the actual duration and lock behavior.

The method inside

  1. Inventory dependencies, compatibility constraints, and current behavior affecting dual-run parity design.
  2. Create reversible seams for behavioral equivalence testing before changing the critical path.
  3. Sequence migration divergence analysis into independently verifiable increments with explicit rollback points.
  4. Keep old and new paths observable until equivalence is proven; remove the fallback only after acceptance criteria pass.

Deliverables

  • Dual-run parity design assessment
  • Behavioral equivalence testing decision and action plan
  • Migration divergence analysis verification checklist

Evidence requirements

  • System risks and architecture boundaries
  • Existing tests, failures, and coverage evidence
  • Release cadence and supported environments

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Apply the migration parity validator to our current dual-run parity design work. We need a concrete decision, bounded changes, and evidence that the result is correct.

Expected output

Start with paired outputs, routing, types, dimensions, timing, failure behavior, representative traffic, and tolerance rules. The highest-risk failure is unit tests passing while the new path drops, renames, reroutes, or aggregates data differently in production. Compare both paths on the same events at the boundary consumers observe and classify every divergence. Verify the result by running a representative replay with forced old-path, new-path, and dual-path failures.

Boundaries and compatibility

Ideal for

  • Dual-run parity design: produce a decision or artifact grounded in supplied evidence.
  • Behavioral equivalence testing: produce a decision or artifact grounded in supplied evidence.
  • Migration divergence analysis: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Chasing line coverage without risk coverage
  • Replacing integration evidence with mocks

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.