planifest/structured-telemetry-mcp/db-migration-strategy

Claude Code and agent skill by planifest/structured-telemetry-mcp

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

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.

Install

npx vskill@latest install planifest/structured-telemetry-mcp/db-migration-strategy

SKILL.md

The same SKILL.md was published earlier as planifest/structured-telemetry-mcp/db-migration-strategy.

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.

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
5

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/planifest/structured-telemetry-mcp/db-migration-strategy/badge)](https://verified-skill.com/skills/planifest/structured-telemetry-mcp/db-migration-strategy)

Something wrong with this skill or its page? Tell us.