devops-rollout-plan

Name: devops-rollout-plan
Author: github

9.4kinstalls4.6kforks

How to install devops-rollout-plan?

github/awesome-copilot/devops-rollout-plan

$npx -y skills add github/awesome-copilot --skill devops-rollout-plan

Installs into the current project.

Summary

Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication plans for infrastructure and application changes

Files · 1

View on GitHub

SKILL.md

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

People who liked this also viewed

6 picks

Type

devops-rollout-plan

9.4kinstalls4.6kforks

View on GitHub

How to install devops-rollout-plan?

github/awesome-copilot/devops-rollout-plan

$npx -y skills add github/awesome-copilot --skill devops-rollout-plan

Installs into the current project.

Summary

Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication plans for infrastructure and application changes

Files · 1

View on GitHub

SKILL.md

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

People who liked this also viewed

6 picks

Type