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 changes'4metadata:5 source: https://skillmd.com/skills/github/devops-rollout-plan6---78# DevOps Rollout Plan Generator910Your goal is to create a comprehensive, production-ready rollout plan for infrastructure or application changes.1112## Input Requirements1314Gather these details before generating the plan:1516### Change Description17- What's changing (infrastructure, application, configuration)18- Version or state transition (from/to)19- Problem solved or feature added2021### Environment Details22- Target environment (dev, staging, production, all)23- Infrastructure type (Kubernetes, VMs, serverless, containers)24- Affected services and dependencies25- Current capacity and scale2627### Constraints & Requirements28- Acceptable downtime window29- Change window restrictions30- Approval requirements31- Regulatory or compliance considerations3233### Risk Assessment34- Blast radius of change35- Data migrations or schema changes36- Rollback complexity and safety37- Known risks3839## Output Format4041Generate a structured rollout plan with these sections:4243### 1. Executive Summary44- What, why, when, duration45- Risk level and rollback time46- Affected systems and user impact47- Expected downtime4849### 2. Prerequisites & Approvals50- Required approvals (technical lead, security, compliance, business)51- Required resources (capacity, backups, monitoring, rollback automation)52- Pre-deployment backups5354### 3. Preflight Checks55- Infrastructure health validation56- Application health baseline57- Dependency availability58- Monitoring baseline metrics59- Go/no-go decision checklist6061### 4. Step-by-Step Rollout Procedure62**Phases**: Pre-deployment, deployment, progressive verification63- Specific commands for each step64- Validation after each step65- Duration estimates6667### 5. Verification Signals68**Immediate** (0-2 min): Deployment success, pods/containers started, health checks passing69**Short-term** (2-5 min): Application responding, error rates acceptable, latency normal70**Medium-term** (5-15 min): Sustained metrics, stable connections, integrations working71**Long-term** (15+ min): No degradation, capacity healthy, business metrics normal7273### 6. Rollback Procedure74**Decision Criteria**: When to initiate rollback75**Rollback Steps**: Automated, infrastructure revert, or full restore76**Post-Rollback Verification**: Confirm system health restored77**Communication**: Stakeholder notification7879### 7. Communication Plan80- Pre-deployment (T-24h): Schedule and impact notice81- Deployment start: Commencement notice82- Progress updates: Status every X minutes83- Completion: Success confirmation84- Rollback (if needed): Issue notification8586**Stakeholder Matrix**: Who to notify, when, via what method, with what content8788### 8. Post-Deployment Tasks89- Immediate (1h): Verify criteria met, review logs90- Short-term (24h): Monitor metrics, review errors91- Medium-term (1 week): Post-deployment review, lessons learned9293### 9. Contingency Plans94Scenarios: Partial failure, performance degradation, data inconsistency, dependency failure95For each: Symptoms, response, timeline9697### 10. Contact Information98- Primary and secondary on-call99- Escalation path100- Emergency contacts (infrastructure, security, database, networking)101102## Plan Customization103104Adapt based on:105- **Infrastructure Type**: Kubernetes, VMs, serverless, databases106- **Risk Level**: Low (simplified), medium (standard), high (additional gates)107- **Change Type**: Code deployment, infrastructure, configuration, data migration108- **Environment**: Production (full plan), staging (simplified), development (minimal)109110## Remember111112- Always have a tested rollback plan113- Communicate early and often114- Monitor metrics, not just logs115- Document everything116- Learn from each deployment117- Never deploy on Friday afternoon (unless critical)118- Never skip verification steps119- Never assume "it should work"