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"
Source: github/awesome-copilot → skills/devops-rollout-plan/SKILL.md
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# DevOps Rollout Plan Generator67Your goal is to create a comprehensive, production-ready rollout plan for infrastructure or application changes.89## Input Requirements1011Gather these details before generating the plan:1213### Change Description14- What's changing (infrastructure, application, configuration)15- Version or state transition (from/to)16- Problem solved or feature added1718### Environment Details19- Target environment (dev, staging, production, all)20- Infrastructure type (Kubernetes, VMs, serverless, containers)21- Affected services and dependencies22- Current capacity and scale2324### Constraints & Requirements25- Acceptable downtime window26- Change window restrictions27- Approval requirements28- Regulatory or compliance considerations2930### Risk Assessment31- Blast radius of change32- Data migrations or schema changes33- Rollback complexity and safety34- Known risks3536## Output Format3738Generate a structured rollout plan with these sections:3940### 1. Executive Summary41- What, why, when, duration42- Risk level and rollback time43- Affected systems and user impact44- Expected downtime4546### 2. Prerequisites & Approvals47- Required approvals (technical lead, security, compliance, business)48- Required resources (capacity, backups, monitoring, rollback automation)49- Pre-deployment backups5051### 3. Preflight Checks52- Infrastructure health validation53- Application health baseline54- Dependency availability55- Monitoring baseline metrics56- Go/no-go decision checklist5758### 4. Step-by-Step Rollout Procedure59**Phases**: Pre-deployment, deployment, progressive verification60- Specific commands for each step61- Validation after each step62- Duration estimates6364### 5. Verification Signals65**Immediate** (0-2 min): Deployment success, pods/containers started, health checks passing66**Short-term** (2-5 min): Application responding, error rates acceptable, latency normal67**Medium-term** (5-15 min): Sustained metrics, stable connections, integrations working68**Long-term** (15+ min): No degradation, capacity healthy, business metrics normal6970### 6. Rollback Procedure71**Decision Criteria**: When to initiate rollback72**Rollback Steps**: Automated, infrastructure revert, or full restore73**Post-Rollback Verification**: Confirm system health restored74**Communication**: Stakeholder notification7576### 7. Communication Plan77- Pre-deployment (T-24h): Schedule and impact notice78- Deployment start: Commencement notice79- Progress updates: Status every X minutes80- Completion: Success confirmation81- Rollback (if needed): Issue notification8283**Stakeholder Matrix**: Who to notify, when, via what method, with what content8485### 8. Post-Deployment Tasks86- Immediate (1h): Verify criteria met, review logs87- Short-term (24h): Monitor metrics, review errors88- Medium-term (1 week): Post-deployment review, lessons learned8990### 9. Contingency Plans91Scenarios: Partial failure, performance degradation, data inconsistency, dependency failure92For each: Symptoms, response, timeline9394### 10. Contact Information95- Primary and secondary on-call96- Escalation path97- Emergency contacts (infrastructure, security, database, networking)9899## Plan Customization100101Adapt based on:102- **Infrastructure Type**: Kubernetes, VMs, serverless, databases103- **Risk Level**: Low (simplified), medium (standard), high (additional gates)104- **Change Type**: Code deployment, infrastructure, configuration, data migration105- **Environment**: Production (full plan), staging (simplified), development (minimal)106107## Remember108109- Always have a tested rollback plan110- Communicate early and often111- Monitor metrics, not just logs112- Document everything113- Learn from each deployment114- Never deploy on Friday afternoon (unless critical)115- Never skip verification steps116- Never assume "it should work"117118---119120**Source:** [`github/awesome-copilot`](https://github.com/github/awesome-copilot) → `skills/devops-rollout-plan/SKILL.md`
thedixitjain