Agent skill · software engineering · wshobson
deployment-pipeline-design
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.
Why this skill is useful
Provides specific architectural patterns and configuration examples for CI/CD pipelines that the AI wouldn't reliably generate on its own.
What it needs
Requires aws-cli, docker, kubectl installed locally. About 3k tokens when loaded. Last updated 2026-08-05. 38,570 stars on the source repository.
What this skill does
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 What This Skill Produces Pipeline configuration: Stage definitions, job dependencies, parallelism, and caching strategy Deployment strategy: Chosen rollout pattern with annotated configuration (canary weights, blue-green switchover, rolling parameters) Health check setup: Shallow vs deep readiness probes, post-deployment smoke test scripts Gate definitions: Automated metric thresholds and manual approval workflows Rollback plan: Automated rollback triggers and manual runbook steps When to Use Design CI/CD architecture for a new service or platform migration Implement deployment gates between environments Configure multi-environment pipelines with mandatory security scanning Establish progressive delivery with canary or blue-green strategies Debug pipelines where stages succeed but production behavior is wrong Reduce mean time to recovery by automating rollback on metric degra …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills wshobson/deployment-pipeline-design