ash1794/vibe-engineering / plugins/vibe-engineering/skills/vibe-rollback-plan
vibe-rollback-plan
VerifiedDocuments rollback procedures before making risky changes. Covers what's changing, verification steps, rollback procedures, and blast radius assessment. Use before database migrations, breaking API changes, infrastructure or DNS changes, large dependency upgrades, or any change where undo is not obvious.
vibe-rollback-plan
The time to plan a rollback is BEFORE you need one.
When to Use This Skill
- Database migrations (especially destructive ones)
- API breaking changes
- Infrastructure changes (networking, permissions, DNS)
- Large dependency upgrades
- Any change where "undo" isn't obvious
When NOT to Use This Skill
- Safe, easily reversible changes (adding a new file, adding a feature flag)
- Changes with automated rollback (CI/CD with rollback built in)
- Local development changes
Steps
-
Document the change:
- What is being changed?
- Why is it being changed?
- What systems are affected?
-
Define success criteria:
- How do we know the change worked?
- What metrics to watch?
- How long to monitor before declaring success?
-
Assess blast radius:
- What breaks if this fails?
- Which users/services are affected?
- Is there data loss risk?
-
Write rollback procedure:
- Step-by-step commands to reverse the change
- Expected time to rollback
- Who needs to be notified?
-
Pre-change checklist:
- Rollback procedure documented
- Rollback tested (if possible)
- Monitoring in place
- Team notified
- Backup taken
Output Format
Rollback Plan: [Change Name]
Change: [Description] Risk Level: Low / Medium / High / Critical Blast Radius: [What's affected] Estimated Recovery Time: [Time to rollback]
Success Criteria
- [How to verify the change worked]
Rollback Procedure
# Step 1: [Description]
[command]
# Step 2: [Description]
[command]
Pre-Change Checklist
- Backup taken
- Rollback tested
- Monitoring active
- Team notified
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |