Devops Rollout Plan
Produce a production-ready rollout document with preflight checks, deployment steps, rollback, and comms before you touch prod.
Overview
DevOps Rollout Plan is an agent skill for the Ship phase that generates comprehensive rollout plans with preflight checks, deployment steps, verification, rollback, and communication for infra and app changes.
Install
npx skills add https://github.com/github/awesome-copilot --skill devops-rollout-planWhat is this skill?
- Structured sections: executive summary, prerequisites, approvals, and risk framing
- Step-by-step deployment with verification signals and rollback procedures
- Captures environment type (K8s, VMs, serverless), blast radius, and data-migration risks
- Communication plan and acceptable downtime aligned to constraints
- Input checklist: change description, targets, compliance, and rollback complexity
- Output includes 2+ major plan sections (executive summary, prerequisites) plus deployment, verification, and rollback bl
Adoption & trust: 9.1k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are about to deploy a risky change but only have tribal knowledge and scattered notes, not a reviewed go-live plan.
Who is it for?
Solo builders preparing staging or production rollouts for Kubernetes, VMs, serverless, or multi-service releases with real downtime or migration risk.
Skip if: Quick local-only config tweaks with zero user impact and no rollback story—use a lighter checklist instead.
When should I use this skill?
You need a comprehensive rollout plan with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication for infrastructure or application changes.
What do I get? / Deliverables
You get a structured rollout plan you can execute, verify, and roll back against—with approvals and comms spelled out before the change window.
- Structured rollout plan document with executive summary, deployment steps, and rollback procedures
Recommended Skills
Journey fit
Rollout planning sits in Ship because it is the gate before releasing infrastructure or application changes to real environments. Launch subphase is where change windows, downtime budgets, and go-live sequencing are decided—not during casual build work.
How it compares
Use for full release runbooks instead of improvising deploy steps in chat without rollback or verification sections.
Common Questions / FAQ
Who is devops-rollout-plan for?
Indie and solo developers who deploy their own stack and need a formal rollout document before production or shared staging changes.
When should I use devops-rollout-plan?
In Ship before a version bump, infra migration, or config rollout—especially when you must document downtime, approvals, and rollback for Kubernetes, VMs, or dependent services.
Is devops-rollout-plan safe to install?
It is procedural documentation guidance; review the Security Audits panel on this page and avoid pasting secrets into prompts when describing environments.
SKILL.md
READMESKILL.md - Devops Rollout Plan
# 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"