deployment-strategy-blue-green
Deployment Strategy Blue Green
Overview
Use this skill to design low-risk cutovers between two production environments with clear rollback paths.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Data/schema compatibility guidance:
references/blue-green-data-compatibility.md
Templates And Assets
- Cutover runbook template:
assets/blue-green-cutover-runbook-template.md
- Readiness checklist:
assets/blue-green-readiness-checklist.md
Inputs To Gather
- Service criticality and acceptable deployment interruption.
- Data/schema compatibility constraints between old/new versions.
- Traffic switching mechanism (LB, DNS, gateway, mesh).
- Health/SLO guardrails and rollback authority.
Deliverables
- Blue-green rollout and cutover plan.
- Readiness checklist for green environment.
- Rollback trigger matrix and execution runbook.
- Post-cutover verification checklist.
Quick Cutover Example
- Deploy to green and run smoke + synthetic checks.
- Mirror a small read-only validation traffic slice.
- Switch 100% traffic at cutover window.
- Rollback immediately if p95/error guardrails breach for N minutes.
Quality Standard
- Green environment parity is validated before switch.
- Cutover decision uses explicit health/SLO criteria.
- Rollback path is operationally tested and time-bounded.
- Stateful compatibility risks are mitigated in advance.
Workflow
- Define cutover/rollback criteria and owners.
- Validate environment parity and dependencies using
assets/blue-green-readiness-checklist.md. - Execute pre-cutover verification in green and capture steps in
assets/blue-green-cutover-runbook-template.md. - Perform controlled traffic switch.
- Monitor guardrails and either stabilize or rollback.
- Decommission blue only after stabilization window.
Failure Conditions
- Stop when rollback cannot be executed within required recovery time.
- Stop when data/schema compatibility between blue/green is unresolved.
- Escalate when guardrails are missing for critical user paths.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9