DevOps Rollout Plan Generator
Your goal is to create a comprehensive, production-ready rollout plan for infrastructure or application changes.
Input Requirements
Gather these details before generating the plan:
Change Description
- What's changing (infrastructure, application, configuration)
- Version or state transition (from/to)
- Problem solved or feature added
Environment Details
- Target environment (dev, staging, production, all)
- Infrastructure type (Kubernetes, VMs, serverless, containers)
- Affected services and dependencies
- Current capacity and scale
Constraints & Requirements
- Acceptable downtime window
- Change window restrictions
- Approval requirements
- Regulatory or compliance considerations
Risk Assessment
- Blast radius of change
- Data migrations or schema changes
- Rollback complexity and safety
- Known risks
Output Format
Generate a structured rollout plan with these sections:
1. Executive Summary
- What, why, when, duration
- Risk level and rollback time
- Affected systems and user impact
- Expected downtime
2. Prerequisites & Approvals
- Required approvals (technical lead, security, compliance, business)
- Required resources (capacity, backups, monitoring, rollback automation)
- Pre-deployment backups
3. Preflight Checks
- Infrastructure health validation
- Application health baseline
- Dependency availability
- Monitoring baseline metrics
- Go/no-go decision checklist
4. Step-by-Step Rollout Procedure
Phases: Pre-deployment, deployment, progressive verification
- Specific commands for each step
- Validation after each step
- Duration estimates
5. Verification Signals
Immediate (0-2 min): Deployment success, pods/containers started, health checks passing
Short-term (2-5 min): Application responding, error rates acceptable, latency normal
Medium-term (5-15 min): Sustained metrics, stable connections, integrations working
Long-term (15+ min): No degradation, capacity healthy, business metrics normal
6. Rollback Procedure
Decision Criteria: When to initiate rollback
Rollback Steps: Automated, infrastructure revert, or full restore
Post-Rollback Verification: Confirm system health restored
Communication: Stakeholder notification
7. Communication Plan
- Pre-deployment (T-24h): Schedule and impact notice
- Deployment start: Commencement notice
- Progress updates: Status every X minutes
- Completion: Success confirmation
- Rollback (if needed): Issue notification
Stakeholder Matrix: Who to notify, when, via what method, with what content
8. Post-Deployment Tasks
- Immediate (1h): Verify criteria met, review logs
- Short-term (24h): Monitor metrics, review errors
- Medium-term (1 week): Post-deployment review, lessons learned
9. Contingency Plans
Scenarios: Partial failure, performance degradation, data inconsistency, dependency failure
For each: Symptoms, response, timeline
10. Contact Information
- Primary and secondary on-call
- Escalation path
- Emergency contacts (infrastructure, security, database, networking)
Plan Customization
Adapt based on:
- Infrastructure Type: Kubernetes, VMs, serverless, databases
- Risk Level: Low (simplified), medium (standard), high (additional gates)
- Change Type: Code deployment, infrastructure, configuration, data migration
- Environment: Production (full plan), staging (simplified), development (minimal)
Remember
- 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 critical)
- Never skip verification steps
- Never assume "it should work"
1---2name: devops-rollout-plan3description: Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication plans for infrastructure and application changes4---5
6# DevOps Rollout Plan Generator
7
8Your goal is to create a comprehensive, production-ready rollout plan for infrastructure or application changes.
9
10## Input Requirements
11
12Gather these details before generating the plan:
13
14### Change Description
15- What's changing (infrastructure, application, configuration)
16- Version or state transition (from/to)
17- Problem solved or feature added
18
19### Environment Details
20- Target environment (dev, staging, production, all)
21- Infrastructure type (Kubernetes, VMs, serverless, containers)
22- Affected services and dependencies
23- Current capacity and scale
24
25### Constraints & Requirements
26- Acceptable downtime window
27- Change window restrictions
28- Approval requirements
29- Regulatory or compliance considerations
30
31### Risk Assessment
32- Blast radius of change
33- Data migrations or schema changes
34- Rollback complexity and safety
35- Known risks
36
37## Output Format
38
39Generate a structured rollout plan with these sections:
40
41### 1. Executive Summary
42- What, why, when, duration
43- Risk level and rollback time
44- Affected systems and user impact
45- Expected downtime
46
47### 2. Prerequisites & Approvals
48- Required approvals (technical lead, security, compliance, business)
49- Required resources (capacity, backups, monitoring, rollback automation)
50- Pre-deployment backups
51
52### 3. Preflight Checks
53- Infrastructure health validation
54- Application health baseline
55- Dependency availability
56- Monitoring baseline metrics
57- Go/no-go decision checklist
58
59### 4. Step-by-Step Rollout Procedure
60**Phases**: Pre-deployment, deployment, progressive verification
61- Specific commands for each step
62- Validation after each step
63- Duration estimates
64
65### 5. Verification Signals
66**Immediate** (0-2 min): Deployment success, pods/containers started, health checks passing
67**Short-term** (2-5 min): Application responding, error rates acceptable, latency normal
68**Medium-term** (5-15 min): Sustained metrics, stable connections, integrations working
69**Long-term** (15+ min): No degradation, capacity healthy, business metrics normal
70
71### 6. Rollback Procedure
72**Decision Criteria**: When to initiate rollback
73**Rollback Steps**: Automated, infrastructure revert, or full restore
74**Post-Rollback Verification**: Confirm system health restored
75**Communication**: Stakeholder notification
76
77### 7. Communication Plan
78- Pre-deployment (T-24h): Schedule and impact notice
79- Deployment start: Commencement notice
80- Progress updates: Status every X minutes
81- Completion: Success confirmation
82- Rollback (if needed): Issue notification
83
84**Stakeholder Matrix**: Who to notify, when, via what method, with what content
85
86### 8. Post-Deployment Tasks
87- Immediate (1h): Verify criteria met, review logs
88- Short-term (24h): Monitor metrics, review errors
89- Medium-term (1 week): Post-deployment review, lessons learned
90
91### 9. Contingency Plans
92Scenarios: Partial failure, performance degradation, data inconsistency, dependency failure
93For each: Symptoms, response, timeline
94
95### 10. Contact Information
96- Primary and secondary on-call
97- Escalation path
98- Emergency contacts (infrastructure, security, database, networking)
99
100## Plan Customization
101
102Adapt based on:
103- **Infrastructure Type**: Kubernetes, VMs, serverless, databases
104- **Risk Level**: Low (simplified), medium (standard), high (additional gates)
105- **Change Type**: Code deployment, infrastructure, configuration, data migration
106- **Environment**: Production (full plan), staging (simplified), development (minimal)
107
108## Remember
109
110- Always have a tested rollback plan
111- Communicate early and often
112- Monitor metrics, not just logs
113- Document everything
114- Learn from each deployment
115- Never deploy on Friday afternoon (unless critical)
116- Never skip verification steps
117- Never assume "it should work"
majiayu000