OneLinersCommand workbench
AI
Back to prompts
plain-prompt

Create an operational rollback plan

Define checkpoints, evidence, ownership, and executable rollback criteria.

Revision
1
Verified
2026-07-26
Save or explore
Save to collectionCreate a collection in the sidebar first.

Compatibility and paths

GenericWorks with instruction-following chat models.
ChatGPT
Claude Code
Gemini CLI

Trust and provenance

Curated record reviewed 2026-07-26. Results still depend on the supplied context and target environment.

Fill variables

Values stay in this browser tab and are not stored.

Generated asset2 required field(s) must be completed
Objective: Produce a rollback that is specific enough to rehearse.

Context: State when rollback is impossible or data restoration is required.

Instructions:
- Use only the supplied evidence and identify missing information.
- Lead with the finding, confidence, and one safe next action.
- Put read-only checks before mutations and include a stop condition.
- Never request or reproduce secrets, credentials, or private keys.

User request:
System/change:
{{environment}}

Planned mutation:
{{evidence}}

Write a rollback plan.

Required output:
- Finding
- Evidence
- Confidence
- Safe next check
- Stop condition

Real example

Input

Upgrade PostgreSQL extension; package can downgrade; extension data format may change

Expected result

Stop condition: extension upgrade reports a new on-disk format. Rollback requires pre-upgrade backup/restore, not package downgrade alone. Rehearse restore on a disposable instance.

Source evidence

PostgreSQL documentationofficial