Agent skill · operations · github
devops-rollout-plan
Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication plans for infrastructure and application changes
Why this skill is useful
Generates a detailed, structured rollout plan that includes specific commands and verification signals tailored for various infrastructure types.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/devops-rollout-plan