Skip to content
cccskills
FreePublished on GitHub

devops-rollout-plan

Create rollout plans for application and infrastructure changes. Organize readiness checks, deployment steps, health indicators, rollback procedures, and stakeholder communications, adapting the detail to the target environment, change type, and level of risk.

OriginalShow the original description

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

Works withKubernetes
See how to install

Good for

  • Prepare a production deployment plan
  • Define rollback steps and decision criteria
  • Set post-deployment health checks
  • Plan stakeholder notifications

Files included (1)

  • SKILL.md3.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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"

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Map an existing codebase into seven documents covering its technology, structure, architecture, conventions, integrations, tests, and concerns. Link findings to file evidence, mark unknowns, and highlight differences between stated plans and the actual implementation.

  • Get oriented in an unfamiliar codebase
  • Prepare documentation for a project handover
  • Compare documented architecture with implementation
github/awesome-copilot40.2KUpdated Oct 17, 2026

Assess a repository’s readiness for AI agents with AgentRC and generate a standalone HTML dashboard. Review scores across nine areas, see prioritized improvements, and optionally apply scoring policies tailored to an organization.

  • Assessing a repository’s readiness for AI agents
  • Prioritizing improvements from assessment results
  • Reviewing scores under an organization’s own policy
github/awesome-copilot40.2KUpdated Oct 17, 2026

Generate coding agent instruction files from a project's actual code using AgentRC. Capture detected languages, frameworks, and conventions in one shared file or split rules by topic and project area, with a preview before writing.

  • Create project instructions for VS Code Copilot
  • Refresh agent rules after project changes
  • Split monorepo instructions by project area
github/awesome-copilot40.2KUpdated Oct 17, 2026

Customize AgentRC readiness assessments to match team or organization standards. Choose or create policies that adjust check importance, disable irrelevant checks, set pass thresholds, and define requirements for automated checks in CI workflows.

  • Set shared readiness standards across an organization
  • Focus assessments on AI tooling
  • Adjust the importance of individual checks
github/awesome-copilot40.2KUpdated Oct 17, 2026

Analyze supplied ad performance data to identify wasted spend, strong campaigns, and next tests. Compare channels, assess whether test differences are meaningful, and produce budget reallocation recommendations with a prioritized action plan.

  • Identify ads and keywords to pause
  • Find campaigns and audiences worth scaling
  • Assess whether A/B test results are meaningful
github/awesome-copilot40.2KUpdated Oct 17, 2026

Turn code files into learning resources by adding comments that explain syntax, programming concepts, and design choices. Adjust explanation depth and repetition to the reader’s knowledge while preserving file structure, encoding, and syntax.

  • Add beginner-friendly explanations to existing code
  • Document the reasoning behind syntax and design choices
  • Adjust comment depth for readers with different experience
github/awesome-copilot40.2KUpdated Oct 17, 2026

See all skills by github

Report a problem with this skill