migration-plan

Generates database schema migration plans with rollback scripts and impact estimates.

105|8|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/686f6c61/alfred-dev --skill migration-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migration-plan
Source: https://github.com/686f6c61/alfred-dev/tree/main/skills/datos/migration-plan
Command: npx skills add https://github.com/686f6c61/alfred-dev --skill migration-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents data loss, extended downtime, and inconsistencies by providing a structured, step-by-step plan for database migrations, including rollback procedures and impact assessments.

Core Features & Use Cases

  • Comprehensive Planning: Generates forward and rollback scripts, estimates impact, and defines verification steps.
  • Risk Mitigation: Ensures changes are backward-compatible and minimizes production disruption.
  • Use Case: When a database schema needs to be updated for a new feature, this Skill will create a detailed plan to safely apply the changes, including how to revert if issues arise, and estimate the potential downtime.

Quick Start

Use the migration-plan skill to create a detailed plan for adding a new 'last_login' timestamp column to the 'users' table.

Frequently Asked Questions about migration-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a database schema migration without causing production downtime?▼

To plan a database schema migration safely, you need a structured approach that generates forward and rollback scripts, estimates impact, and defines verification steps to ensure data integrity and minimize downtime.

What is the best way to create a rollback strategy for an ALTER TABLE statement?▼

The best way to create a rollback strategy for an ALTER TABLE statement is to develop a comprehensive migration plan that includes reverse scripts and verification procedures to restore the previous schema state if issues arise.

How do I estimate the impact of database schema changes before applying them?▼

You estimate the impact of database schema changes by developing a migration plan that assesses potential downtime, evaluates backward compatibility, and outlines verification procedures before executing forward scripts in production.

Can I use a migration plan for data transformations in production environments?▼

Yes, you can use a migration plan for data transformations in production environments. It ensures changes are backward-compatible, addresses data integrity, and minimizes production disruption through rigorous planning and rollback strategies.

When do I need a database migration plan for adding a new column to an existing table?▼

You need a database migration plan when adding a new column to ensure the schema update is backward-compatible, includes a rollback procedure, and estimates potential downtime to prevent production data inconsistencies.

What are the limitations of planning database migrations without rollback scripts?▼

Planning database migrations without rollback scripts risks extended downtime and data loss, because you lack a verified procedure to revert schema changes or data transformations if production issues occur during the update.