Attribution: Sourced from github/awesome-copilot by GitHub Community, licensed MIT. Modified for this collection.
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: >-4 Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification5 signals, rollback procedures, and communication plans for infrastructure and application changes.6 Use before deploying a risky infrastructure or application change to production.7license: MIT8source: "https://github.com/github/awesome-copilot"9attribution: "github/awesome-copilot by GitHub Community"10metadata:11 source: https://skillmd.com/skills/mouadja02/devops-rollout-plan12---1314> **Attribution:** Sourced from [github/awesome-copilot](https://github.com/github/awesome-copilot) by [GitHub Community](https://github.com/github), licensed MIT. Modified for this collection.1516# DevOps Rollout Plan Generator1718Your goal is to create a comprehensive, production-ready rollout plan for infrastructure or application changes.1920## Input Requirements2122Gather these details before generating the plan:2324### Change Description25- What's changing (infrastructure, application, configuration)26- Version or state transition (from/to)27- Problem solved or feature added2829### Environment Details30- Target environment (dev, staging, production, all)31- Infrastructure type (Kubernetes, VMs, serverless, containers)32- Affected services and dependencies33- Current capacity and scale3435### Constraints & Requirements36- Acceptable downtime window37- Change window restrictions38- Approval requirements39- Regulatory or compliance considerations4041### Risk Assessment42- Blast radius of change43- Data migrations or schema changes44- Rollback complexity and safety45- Known risks4647## Output Format4849Generate a structured rollout plan with these sections:5051### 1. Executive Summary52- What, why, when, duration53- Risk level and rollback time54- Affected systems and user impact55- Expected downtime5657### 2. Prerequisites & Approvals58- Required approvals (technical lead, security, compliance, business)59- Required resources (capacity, backups, monitoring, rollback automation)60- Pre-deployment backups6162### 3. Preflight Checks63- Infrastructure health validation64- Application health baseline65- Dependency availability66- Monitoring baseline metrics67- Go/no-go decision checklist6869### 4. Step-by-Step Rollout Procedure70**Phases**: Pre-deployment, deployment, progressive verification71- Specific commands for each step72- Validation after each step73- Duration estimates7475### 5. Verification Signals76**Immediate** (0-2 min): Deployment success, pods/containers started, health checks passing77**Short-term** (2-5 min): Application responding, error rates acceptable, latency normal78**Medium-term** (5-15 min): Sustained metrics, stable connections, integrations working79**Long-term** (15+ min): No degradation, capacity healthy, business metrics normal8081### 6. Rollback Procedure82**Decision Criteria**: When to initiate rollback83**Rollback Steps**: Automated, infrastructure revert, or full restore84**Post-Rollback Verification**: Confirm system health restored85**Communication**: Stakeholder notification8687### 7. Communication Plan88- Pre-deployment (T-24h): Schedule and impact notice89- Deployment start: Commencement notice90- Progress updates: Status every X minutes91- Completion: Success confirmation92- Rollback (if needed): Issue notification9394**Stakeholder Matrix**: Who to notify, when, via what method, with what content9596### 8. Post-Deployment Tasks97- Immediate (1h): Verify criteria met, review logs98- Short-term (24h): Monitor metrics, review errors99- Medium-term (1 week): Post-deployment review, lessons learned100101### 9. Contingency Plans102Scenarios: Partial failure, performance degradation, data inconsistency, dependency failure103For each: Symptoms, response, timeline104105### 10. Contact Information106- Primary and secondary on-call107- Escalation path108- Emergency contacts (infrastructure, security, database, networking)109110## Plan Customization111112Adapt based on:113- **Infrastructure Type**: Kubernetes, VMs, serverless, databases114- **Risk Level**: Low (simplified), medium (standard), high (additional gates)115- **Change Type**: Code deployment, infrastructure, configuration, data migration116- **Environment**: Production (full plan), staging (simplified), development (minimal)117118## Remember119120- Always have a tested rollback plan121- Communicate early and often122- Monitor metrics, not just logs123- Document everything124- Learn from each deployment125- Never deploy on Friday afternoon (unless critical)126- Never skip verification steps127- Never assume "it should work"