Decides whether to roll back or roll forward a bad release using a fixed procedure (data compatibility between versions, current migration phase, measured time to revert versus time to fix, customer impact rate), gives the exact order of operations for flag kill, traffic drain, app rollback, and migration reversal, and lists what can never be reversed and how to compensate instead. Writes the Rollback plan section of the Release Dossier before the release and the executed decision into the incident log during one. Use when someone asks "should we roll back", "revert or hotfix", "can we roll back after the migration ran", "what's our rollback plan", "the deploy is broken, what do we do first", or when progressive-rollout gates abort. Do NOT use for running the incident itself - use incident-command instead; for designing migration phases, use zero-downtime-db-migrations.
---
name: rollback-or-roll-forward
description: Decides whether to roll back or roll forward a bad release using a fixed procedure (data compatibility between versions, current migration phase, measured time to revert versus time to fix, customer impact rate), gives the exact order of operations for flag kill, traffic drain, app rollback, and migration reversal, and lists what can never be reversed and how to compensate instead. Writes the Rollback plan section of the Release Dossier before the release and the executed decision into the incident log during one. Use when someone asks "should we roll back", "revert or hotfix", "can we roll back after the migration ran", "what's our rollback plan", "the deploy is broken, what do we do first", or when progressive-rollout gates abort. Do NOT use for running the incident itself - use incident-command instead; for designing migration phases, use zero-downtime-db-migrations.
---
… premium skill: the full instructions load in your AI once you have access.