deployment-pipeline-design

SKILL.md

Multi-stage CI/CD pipelines with approval gates and deployment orchestration.

Covers four deployment strategies: rolling updates, blue-green, canary, and feature flags, each with trade-offs for downtime, rollback speed, and infrastructure cost

Includes approval gate patterns for manual review, time-based delays, and multi-approver workflows across GitHub Actions, GitLab CI, and Azure Pipelines

Provides automated rollback mechanisms triggered by health checks and failure detection, plus manual rollback commands for Kubernetes deployments

Outlines nine-stage pipeline flow from source checkout through build, test, staging, approval, production deployment, and verification with monitoring integration

Deployment Pipeline Design

Architecture patterns for multi-stage CI/CD pipelines with approval gates, deployment strategies, and environment promotion workflows.

Purpose

Design robust, secure deployment pipelines that balance speed with safety through proper stage organization, automated quality gates, and progressive delivery strategies. This skill covers both the structural design of pipeline architecture and the operational patterns for reliable production deployments.

Input / Output

What You Provide

Application type: Language/runtime, containerized or bare-metal, monolith or microservices

Deployment target: Kubernetes, ECS, VMs, serverless, or platform-as-a-service

Environment topology: Number of environments (dev/staging/prod), region layout, air-gap requirements

Rollout requirements: Acceptable downtime, rollback SLA, traffic splitting needs, canary vs blue-green preference

Gate constraints: Approval teams, required test coverage thresholds, compliance scans (SAST, DAST, SCA)

Monitoring stack: Prometheus, Datadog, CloudWatch, or other metrics sources used for automated promotion decisions