rollback-plan
Write a concrete rollback plan for a risky change (deploy, migration, feature-flag flip, config rollout) so the reverse is one command away — not an improvised debate at 2am. Use when asked to write a rollback plan, back-out plan, revert plan, or 'what if we need to undo this'. Produces a rollback plan with the signals that trigger it, exact reverse commands, verification steps, data-safety notes, and a communications template.
npx skills add mohitagw15856/pm-claude-skills --skill rollback-plan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Rollback Plan Skill Turns "we'll roll back if it goes bad" into a plan somebody unfamiliar with the change can execute under pressure. The single job: make the reverse of the change knowable, verifiable, and boring. ## Working from a brief Deliver the full plan even from a thin brief — infer and label assumptions (never invent service names, dashboard URLs, commit SHAs, or migration IDs). If a required input is missing, ask once, then move on with `unknown — confirm before rollout` placeholders. ## Required Inputs Ask for (if not already provided), else label as unknown: - **The change** — what's shipping, service(s) affected, blast radius. - **How it ships** — deploy pipeline, feature-flag key, migration ID, config path. - **Rollout shape** — big-bang, staged (X% → Y% → 100%), canary, region-by-region. - **Data implications** — does it write new schema/data, change the meaning of existing columns, backfill, encrypt-in-place, delete? Reversible in-place or one-way? - **Downstream consumers** — services / queues / clients that read the changed contract. - **Trigger conditions** — the SLIs / dashboards / alerts that would tell us it's bad (be specific: metric, threshold, duration).
- Working from a brief
- Required Inputs
- Output Format
- Quality Checks
- Anti-Patterns
- Example Trigger Phrases
What does the rollback-plan skill do?
Write a concrete rollback plan for a risky change (deploy, migration, feature-flag flip, config rollout) so the reverse is one command away — not an improvised debate at 2am. Use when asked to write a rollback plan, back-out plan, revert plan, or 'what if we need to undo this'. Produces a rollback plan with the signals that trigger it, exact reverse commands, verification steps, data-safety notes, and a communications template.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill rollback-plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.