Devops Rollout Plan

DevOps rollout plan

Create a comprehensive step-by-step rollout plan that turns a proposed infrastructure or application change into a preflighted, observable, reversible production deployment with communication, rollback, and contingency paths.

When to invoke

• "Generate a rollout plan for this deployment."
• "Create a production change plan."
• "Write preflight checks, rollout steps, verification, and rollback."
• "Plan this Kubernetes, VM, serverless, or container release."
• "Prepare a go/no-go checklist for an infrastructure change."

Inputs

Use $ARGUMENTS as the change description, environment, or target system when provided. If details are missing, collect enough to avoid a generic plan.

Rollout structure

Verification windows

Customization rules

Rollout principles

• Always have a tested rollback plan.
• Communicate early and often.
• Monitor metrics, not just logs.
• Document everything.
• Learn from each deployment.
• Never deploy on Friday afternoon unless the change is critical.
• Never skip verification steps.
• Never assume "it should work".

Output template

# Rollout Plan: <change name>

## 1. Executive Summary
- What: <change>
- Why: <reason>
- When: <window>
- Duration: <estimate>
- Risk level: low | medium | high
- Rollback time: <estimate>
- Affected systems: <systems>
- User impact / expected downtime: <impact>

## 2. Prerequisites & Approvals
| Requirement | Owner | Status |
| --- | --- | --- |
| Technical lead approval | <name> | pending |

## 3. Preflight Checks
- [ ] Infrastructure health baseline captured.
- [ ] Application health baseline captured.
- [ ] Dependencies available.
- [ ] Monitoring baseline metrics captured.
- [ ] Go/no-go decision recorded.

## 4. Step-by-Step Rollout Procedure
| Phase | Step | Command/action | Validation | Duration |
| --- | --- | --- | --- | --- |
| Pre-deployment | <step> | `<command>` | <signal> | <time> |

## 5. Verification Signals
| Window | Signals | Pass criteria |
| --- | --- | --- |
| Immediate (0-2 min) | deployment, pods/containers, health checks | <criteria> |
| Short-term (2-5 min) | response, error rate, latency | <criteria> |
| Medium-term (5-15 min) | sustained metrics, connections, integrations | <criteria> |
| Long-term (15+ min) | degradation, capacity, business metrics | <criteria> |

## 6. Rollback Procedure
**Decision criteria:** <when to rollback>
**Steps:** <automated/infrastructure/full restore steps>
**Post-rollback verification:** <checks>
**Communication:** <notification>

## 7. Communication Plan
| Time | Audience | Channel | Message |
| --- | --- | --- | --- |
| T-24h | <stakeholders> | <channel> | <notice> |

## 8. Post-Deployment Tasks
- Immediate (1h): <tasks>
- Short-term (24h): <tasks>
- Medium-term (1 week): <tasks>

## 9. Contingency Plans
| Scenario | Symptoms | Response | Timeline |
| --- | --- | --- | --- |
| Partial failure | <symptoms> | <response> | <time> |

## 10. Contact Information
| Role | Primary | Secondary | Escalation |
| --- | --- | --- | --- |
| On-call | <person> | <person> | <path> |

Quality gate

• Change description, environment, constraints, and risk assessment are captured.
• The plan includes all ten sections from Executive Summary through Contact Information.
• Preflight checks include infrastructure, application, dependencies, monitoring, and go/no-go.
• Rollout steps include commands/actions, validation after each step, and duration estimates.
• Verification signals cover 0-2 min, 2-5 min, 5-15 min, and 15+ min windows.
• Rollback has decision criteria, steps, post-rollback verification, and communication.
• Communication includes T-24h, deployment start, progress updates, completion, and rollback notices.
• Contingencies cover partial failure, performance degradation, data inconsistency, and dependency failure.