agentleFS
imtiazrayhanimtiazrayhan/agentscamp-library/skills/rollback-plan-writer/SKILL.md

rollback-plan-writer

Skill1 starsChanged 6 days agoMITView on GitHub

Write a tested rollback and forward-recovery plan for a release, including triggers, commands, compatibility constraints, data handling, verification, ownership, and stop conditions. Use before high-risk deploys, schema or configuration changes, dependency upgrades, model or provider migrations, feature launches, and any release where 'just redeploy the old version' is incomplete or unsafe.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write a plan responders can execute under pressure.

    line 8
  2. Distinctive:

    Set objective triggers: Use error rate, latency, correctness, data integrity, SLO burn, queue depth, or business metrics with thresholds …

    line 13
  3. Distinctive:

    Verify recovery: Use the same health and business checks as the release gate.

    line 19
  4. Distinctive:

    Create a Markdown rollback plan containing:

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Write a plan responders can execute under pressure. Verify commands against repository and deployment configuration; label anything that cannot be confirmed.

Workflow

  1. Define release scope. List application artifacts, database migrations, configuration, feature flags, secrets, caches, queues, scheduled jobs, infrastructure, APIs, models/providers, and external dependencies changing together.
  2. Set objective triggers. Use error rate, latency, correctness, data integrity, SLO burn, queue depth, or business metrics with thresholds and observation windows. Name who declares rollback.
  3. Check compatibility in both directions. Confirm old code can run against new schema and data, new code can run during partial rollout, events remain readable, and configuration and secrets can be restored. Identify the point after which rollback becomes unsafe.
  4. Choose recovery paths. Define fast disable or feature-flag containment, application rollback, configuration rollback, traffic shift, and forward fix. State when each applies and when to stop trying it.
  5. Protect data. Describe dual-write or expand-contract phases, write freezes, backups or exports, reconciliation, queued-message handling, and irreversible effects. Never invent a down migration for data that cannot be reconstructed.
  6. Write exact commands. Mine workflow files, deployment manifests, runbooks, and scripts for artifact IDs, environments, namespaces, revisions, and flags. Include expected output and the next decision.
  7. Assign roles and communication. Name release lead, executor, verifier, database or platform owner, and communication owner. Include escalation thresholds and stakeholder channels.
  8. Verify recovery. Use the same health and business checks as the release gate. Define how long metrics must remain healthy, how data is reconciled, and which temporary containment steps must be removed.
  9. Rehearse. Dry-run commands in a safe environment or tabletop the sequence. Record untested assumptions and block the release when the only recovery path is speculative.

[!WARNING] A rollback command that has not been checked against the current deployment configuration is a hypothesis. Label it unverified and test it before approving the release.

Output

Create a Markdown rollback plan containing:

  • release inventory and compatibility matrix
  • trigger table with threshold, observation window, and decision owner
  • containment, rollback, and forward-recovery decision tree
  • exact commands with expected results and stop conditions
  • database, event, cache, and external-side-effect handling
  • roles, escalation, and communication
  • verification and observation checklist
  • rehearsal results, untested assumptions, and rollback cutoff point

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.