Skills

Skill 136 of 200

DevOps Rollout Plan

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

2 minutes · 442 words · 19 sections

Install

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

$ npx skills add github/awesome-copilot

» /plugin marketplace add github/awesome-copilot

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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

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”

About this skill

Trigger

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

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/github/awesome-copilot, branch main, last pushed 24 September 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

200 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 2 distinct layouts observed: .github/skills/*/SKILL.md, skills/*/SKILL.md.

Authorship

3 of 200 skills are installed into the repository rather than published from it. They are shelved in the closing “Credited skills” part and remain the work of their own authors. A skill counts as credited when its only copy lives under one agent’s dot directory; visible directories, per-agent mirror sets, and skills installable from this repository on skills.sh all count as published.

Issue colours

Resolved from a curated brand profile — hue 295°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “19 headings” from h1 to h2 so the skill title is the only h1.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .github/plugin/marketplace.json by GitHub, declaring 162 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /github/awesome-copilot.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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

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”