Index of every page on this site: llms.txt
All skills
github avatar

/devops-rollout-plan

@f10fdb8 official
by githubgithub/awesome-copilot41k stars
5,399
Run it yourself

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

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/devops-rollout-plan

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈54 tokens for metadata: the name and description. ≈937 when used: this file.

Description uses 2.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈216 characters, or 2.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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"

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill is a purely instructional template for generating DevOps rollout plans and does not contain any executable code, network operations, or security risks.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at f10fdb8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 9 months ago
  • DevOps
  • Infrastructure
  • rollout
  • deployment
  • kubernetes
  • rollback
  • monitoring
  • change-management
  • verification
  • communication

README badge

README badge for github/awesome-copilot/devops-rollout-plan

Generates structured rollout plans for infrastructure and application changes, including preflight checks, step-by-step deployment procedures, verification signals at different timescales, rollback procedures, and communication templates. Use this when planning Kubernetes deployments, VM migrations, configuration changes, or database schema updates where you need documented go/no-go decisions and stakeholder notification workflows.

Generated from the current SKILL.md.

Does this skill generate rollout plans for any infrastructure type?
Yes. It adapts to Kubernetes, VMs, serverless, containers, and databases. The plan customizes based on your infrastructure type and risk level.
What information do I need to provide to generate a plan?
You need to describe the change (what, version transition, problem solved), target environment, affected services, acceptable downtime, and risk assessment including blast radius and rollback complexity.
Does this skill include rollback procedures?
Yes. The plan includes rollback decision criteria, step-by-step rollback steps, post-rollback verification, and stakeholder communication for the rollback scenario.
Can I use this for production deployments?
Yes. The skill is designed for production-ready rollout plans and includes full approval workflows, preflight checks, verification signals across multiple timescales, and contingency scenarios.
Does this generate communication templates?
Yes. It includes a communication plan with pre-deployment, deployment start, progress updates, completion, and rollback notifications, plus a stakeholder matrix with timing and methods.

Generated from the current SKILL.md. These answers refresh after source changes.