Agent skill · software engineering · sickn33
deployment-pipeline-design
Architecture patterns for multi-stage CI/CD pipelines with approval gates and deployment strategies.
Why this skill is useful
Provides specific deployment strategies and CI/CD pipeline patterns that the AI wouldn't reliably generate on its own.
What it needs
Requires git, kubectl installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Deployment Pipeline Design Architecture patterns for multi-stage CI/CD pipelines with approval gates and deployment strategies. Do not use this skill when The task is unrelated to deployment pipeline design You need a different domain or tool outside this scope Instructions Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes. Provide actionable steps and verification. Purpose Design robust, secure deployment pipelines that balance speed with safety through proper stage organization and approval workflows. Use this skill when Design CI/CD architecture Implement deployment gates Configure multi-environment pipelines Establish deployment best practices Implement progressive delivery Pipeline Stages Standard Pipeline Flow Detailed Stage Breakdown 1. Source - Code checkout 2. Build - Compile, package, containerize 3. Test - Unit, integration, security scans 4. Staging Deploy - Deploy to staging environment 5. Integration Tests - E2E, smoke tests 6. Approval Gate - Manual approval required 7. Production Deploy - Canary, blue-green, rolling 8. Verification - Health checks, monitoring 9. Rollback - Automated rollback on failure Approval Gate Patterns Pattern 1: Manual Approval Pattern 2: Delayed Deployment Pattern 3: Multi-Approver Configure the platform's actual protected-environment approval policy and verify who may approve or bypass it. For Azure, bind manual validation to the installed task version and its supported agentless job rather than placing it in an arbitrary deployment hook. Record required approvers and evidence; notifications alone are not approval. Deployment Strategies 1. Rolling Deployment Characteristics: Gradual rollout Availability depends on readiness, capacity and compatible changes Easy rollback Best for most applications 2. Blue-Green Deployment Characteristics: Instant switchover Easy rollback Doubles infrastructure cost temporarily Good for high-risk deployments 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/deployment-pipeline-design--ea017d