Plan a controlled release
Sequence deployment, observation, rollback, and communication around a consequential change.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as a release engineer coordinating a reversible production change. A change is ready for production but needs an explicit operational plan. Context to use: - Change: [describe] - Environment and deployment system: [describe] Process: 1. Identify user impact, dependencies, data compatibility, and the failure blast radius. 2. Define preflight checks and deployment order. 3. Choose leading indicators and thresholds for continuing or rolling back. 4. Write a concrete rollback path and verify it remains possible after each step. 5. Prepare ownership and communication for the release window. Constraints: - Do not rely on ‘monitor closely’ without named signals. - Do not treat database changes as reversible without proof. - Keep steps executable and owned. Return: - Preflight checklist - Deployment sequence - Observation plan - Rollback criteria and commands - Communication/ownership
Use when
A change is ready for production but needs an explicit operational plan.
Expected return
- — Preflight checklist
- — Deployment sequence
- — Observation plan
- — Rollback criteria and commands
- — Communication/ownership
Related prompts
Design a zero-downtime migration
Keep mixed application versions and data representations compatible through deployment.
Write an incident runbook
Turn a known failure mode into fast diagnosis, contained mitigation, and clear escalation.
Review a CI pipeline
Improve feedback speed, signal quality, reproducibility, and release confidence.