SkillHub

Skills github awesome-copilot

devops-rollout-plan

Use it when:
You're about to ship an infrastructure, application, configuration or data change and want a written plan for doing it safely.
It does:
Gathers what's changing, the environment, constraints and risks, then fills a ten-section rollout template.
You get:
A plan with go/no-go checks, step commands with validation and timings, timed verification signals, rollback criteria and steps, and a stakeholder communication schedule.
Scales:
Down for low-risk or staging changes, and up with extra gates for high-risk production ones.

TL;DR

A planning template for change management. Before writing, the agent needs the change and its from-to versions, the target environment and infrastructure type such as Kubernetes, VMs or serverless, affected services, downtime and change windows, approvals and compliance needs, and the risks: blast radius, data migrations and how hard rollback would be. The plan then covers an executive summary with risk level and expected downtime; prerequisites, approvals and backups; preflight health checks with a go/no-go checklist; the rollout in phases, with specific commands, validation after each step and duration estimates; verification signals at 0-2, 2-5, 5-15 and 15+ minutes; rollback criteria, steps and checks; a communication plan from 24 hours before, with a stakeholder matrix; post-deployment tasks; contingency plans for partial failure, degraded performance, data inconsistency and dependency failure; and on-call contacts and escalation. Its closing rules include always having a tested rollback, monitoring metrics and not only logs, and never deploying on a Friday afternoon unless critical.

Summarizes the skill at 797337f.

npx skills add https://github.com/github/awesome-copilot --skill devops-rollout-plan

skills.sh pageSource on GitHubAll skills from github/awesome-copilot

Total Downloads
9,700 on skills.sh, Nov 9, 2026
Repo stars
40,943 github/awesome-copilot
First seen
Feb 25, 2026 on skills.sh
Weekly Downloads
10
-55% over the 8 weeks to Nov 9
Weekly values
Week toInstalls
Sep 2122
Sep 2832
Oct 527
Oct 1216
Oct 199
Oct 2613
Nov 216
Nov 910
Category
category:cloudcategory:software-engineering

Deploy, provision, observe and debug cloud apps.

Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.
Type
type:command

A one-shot action you invoke by name, such as turning the conversation into a PRD.
Effect
effect:none

Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.
Needs
needs:none

Instructions only. Works in any agent that supports skills.
Publisher
by:official

A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates.
Topics
deploymentplanninginfrastructure

SKILL.md

From github/awesome-copilot at 797337f. Checked daily, last changed Nov 6, 2026.

Frontmatter
name: devops-rollout-plan
description: 'Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication plans for infrastructure and application changes'

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"