jeremylongworth-source Rollback Plan
Core Workflow
- Identify change type, affected users, state changes, data migrations, and dependencies.
- Define rollback triggers, decision owner, time window, and monitoring signals.
- Document rollback steps, fallback alternatives, feature-flag switches, restore procedures, and verification checks.
- Separate reversible code/config changes from irreversible data changes.
- Include customer/support communication and incident handoff when relevant.
- Add post-rollback validation and follow-up actions.
Safety Rules
- Do not claim rollback is possible when data or external side effects are irreversible.
- Do not run rollback commands or restore data without explicit approval.
- Escalate rollbacks involving migrations, payments, auth, customer data, or regulatory impact.
Deliverable Shape
For rollback plans, provide:
- Change scope
- Rollback triggers and owner
- Reversible and irreversible parts
- Rollback steps
- Fallback path
- Validation checks
- Communication plan
- Follow-up actions
References
- Read
references/rollback-plan-checklist.mdwhen preparing rollback or fallback plans.