Prompt file imported from dhar174/tiny_village (.github/prompts/devops-rollout-plan.prompt.md). Copyright stays with the author.

DevOps Rollout Plan Generator

Name: devops-rollout-plan
Author: dhar174

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"

# 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"

{ "prompt": "# DevOps Rollout Plan Generator\r\n\r\nYour goal is to create a comprehensive, production-ready rollout plan for infrastructure or application changes.\r\n\r\n## Input Requirements\r\n\r\nGather these details before generating the plan:\r\n\r\n### Change Description\r\n- What's changing (infrastructure, application, configuration)\r\n- Version or state transition (from/to)\r\n- Problem solved or feature added\r\n\r\n### Environment Details\r\n- Target environment (dev, staging, production, all)\r\n- Infrastructure type (Kubernetes, VMs, serverless, containers)\r\n- Affected services and dependencies\r\n- Current capacity and scale\r\n\r\n### Constraints & Requirements\r\n- Acceptable downtime window\r\n- Change window restrictions\r\n- Approval requirements\r\n- Regulatory or compliance considerations\r\n\r\n### Risk Assessment\r\n- Blast radius of change\r\n- Data migrations or schema changes\r\n- Rollback complexity and safety\r\n- Known risks\r\n\r\n## Output Format\r\n\r\nGenerate a structured rollout plan with these sections:\r\n\r\n### 1. Executive Summary\r\n- What, why, when, duration\r\n- Risk level and rollback time\r\n- Affected systems and user impact\r\n- Expected downtime\r\n\r\n### 2. Prerequisites & Approvals\r\n- Required approvals (technical lead, security, compliance, business)\r\n- Required resources (capacity, backups, monitoring, rollback automation)\r\n- Pre-deployment backups\r\n\r\n### 3. Preflight Checks\r\n- Infrastructure health validation\r\n- Application health baseline\r\n- Dependency availability\r\n- Monitoring baseline metrics\r\n- Go/no-go decision checklist\r\n\r\n### 4. Step-by-Step Rollout Procedure\r\n**Phases**: Pre-deployment, deployment, progressive verification\r\n- Specific commands for each step\r\n- Validation after each step\r\n- Duration estimates\r\n\r\n### 5. Verification Signals\r\n**Immediate** (0-2 min): Deployment success, pods/containers started, health checks passing\r\n**Short-term** (2-5 min): Application responding, error rates acceptable, latency normal\r\n**Medium-term** (5-15 min): Sustained metrics, stable connections, integrations working\r\n**Long-term** (15+ min): No degradation, capacity healthy, business metrics normal\r\n\r\n### 6. Rollback Procedure\r\n**Decision Criteria**: When to initiate rollback\r\n**Rollback Steps**: Automated, infrastructure revert, or full restore\r\n**Post-Rollback Verification**: Confirm system health restored\r\n**Communication**: Stakeholder notification\r\n\r\n### 7. Communication Plan\r\n- Pre-deployment (T-24h): Schedule and impact notice\r\n- Deployment start: Commencement notice\r\n- Progress updates: Status every X minutes\r\n- Completion: Success confirmation\r\n- Rollback (if needed): Issue notification\r\n\r\n**Stakeholder Matrix**: Who to notify, when, via what method, with what content\r\n\r\n### 8. Post-Deployment Tasks\r\n- Immediate (1h): Verify criteria met, review logs\r\n- Short-term (24h): Monitor metrics, review errors\r\n- Medium-term (1 week): Post-deployment review, lessons learned\r\n\r\n### 9. Contingency Plans\r\nScenarios: Partial failure, performance degradation, data inconsistency, dependency failure\r\nFor each: Symptoms, response, timeline\r\n\r\n### 10. Contact Information\r\n- Primary and secondary on-call\r\n- Escalation path\r\n- Emergency contacts (infrastructure, security, database, networking)\r\n\r\n## Plan Customization\r\n\r\nAdapt based on:\r\n- **Infrastructure Type**: Kubernetes, VMs, serverless, databases\r\n- **Risk Level**: Low (simplified), medium (standard), high (additional gates)\r\n- **Change Type**: Code deployment, infrastructure, configuration, data migration\r\n- **Environment**: Production (full plan), staging (simplified), development (minimal)\r\n\r\n## Remember\r\n\r\n- Always have a tested rollback plan\r\n- Communicate early and often\r\n- Monitor metrics, not just logs\r\n- Document everything\r\n- Learn from each deployment\r\n- Never deploy on Friday afternoon (unless critical)\r\n- Never skip verification steps\r\n- Never assume \"it should work\"", "variables": [], "notes": "Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication plans for infrastructure and application changes Tools: codebase, terminalCommand, search, githubRepo.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/dhar174/tiny_village", "path": ".github/prompts/devops-rollout-plan.prompt.md", "ref": "de134632bd4832087dac49f5819a75d2e0aa0747", "url": "https://github.com/dhar174/tiny_village/blob/de134632bd4832087dac49f5819a75d2e0aa0747/.github/prompts/devops-rollout-plan.prompt.md", "key": "dhar174/tiny_village/.github/prompts/devops-rollout-plan.prompt.md" } } }

devops-rollout-plan

About