agentsclimarketplace

Db migration strategy

Skill planifest/planifest-framework/planifest-framework/external-skills/db-migration-strategy

A specification framework for agentic development. Agents build from complete specs - not guesses.

Install
npx -y skills add planifest/planifest-framework --skill db-migration-strategy

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Schema migration strategy workflow for sequencing changes, compatibility windows, and rollback-safe rollout in live systems. Use when schema evolution impacts running services; do not use for static greenfield schemas without deployment constraints.

SKILL.md

1.9 KB, 309 tokens by cl100k_base, as published. Nobody here has run it

DB Migration Strategy

Overview

Use this skill to evolve schemas in production without service disruption or hidden data corruption.

Scope Boundaries

  • Schema changes affect live read/write paths.
  • Multiple service versions must coexist during rollout.
  • Data backfill or contract transition is required.

Core Judgments

  • Migration pattern: expand-contract, dual-write, shadow-read, or phased cutover.
  • Compatibility window duration and supported versions.
  • Backfill approach and execution safety.
  • Rollback semantics and data reconciliation strategy.

Practitioner Heuristics

  • Prefer additive/compatible changes before destructive cleanup.
  • Separate schema deployment from application behavior switch.
  • Dual-write without reconciliation plan is a corruption risk.
  • Large backfills need throttling and progress observability tied to business impact.

Workflow

  1. Define change classes: additive, transitional, destructive.
  2. Sequence schema and application releases for compatibility.
  3. Plan data migration/backfill and failure handling.
  4. Define cutover trigger and rollback decision points.
  5. Execute deprecation/removal only after compatibility window closes.
  6. Document residual migration debt and retirement deadlines.

Common Failure Modes

  • Breaking changes shipped before all consumers are updated.
  • Backfill jobs compete with production traffic and cause incidents.
  • Rollback plan restores code but not data semantics.

Failure Conditions

  • Stop when compatibility window cannot be supported operationally.
  • Stop when rollback semantics for migrated data are undefined.
  • Escalate when migration risk exceeds release risk tolerance.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.