# Rollback Plan

> Create rollback and fallback plans for deployments, releases, migrations, feature flags, and production changes. Use when Codex is asked to define rollback triggers, recovery steps, data restore needs, communication, or post-rollback validation.

- Skill: `jeremylongworth-source/rollback-plan` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add jeremylongworth-source/rollback-plan`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jeremylongworth-source/rollback-plan/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: jeremylongworth-source (https://skillmd.com/u/jeremylongworth-source)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/jeremylongworth-source/rollback-plan

---


# Rollback Plan

## Core Workflow

1. Identify change type, affected users, state changes, data migrations, and
   dependencies.
2. Define rollback triggers, decision owner, time window, and monitoring
   signals.
3. Document rollback steps, fallback alternatives, feature-flag switches,
   restore procedures, and verification checks.
4. Separate reversible code/config changes from irreversible data changes.
5. Include customer/support communication and incident handoff when relevant.
6. 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.md` when preparing rollback or
  fallback plans.