Agent skill · software engineering · rmyndharis
deployment-pipeline-design
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
Why this skill is useful
Provides specific YAML configurations for CI/CD pipelines that are not commonly found in public documentation.
What it needs
About 4k tokens when loaded. Last updated 2026-08-02. 1,255 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: Time-Based Approval Pattern 3: Multi-Approver Deployment Strategies 1. Rolling Deployment Characteristics: Gradual rollout Zero downtime 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. Canary Deployment Characteristics: Gradual traffic shift Risk mitigation Real user testing Requires service mesh or similar 4. Feature Flags Characteristics: Deploy without releasing A/B testing Instant rollback Granular control Pipeline Orchestration Multi-Stage Pipeline Example Pipeline Best Practices 1. Fail fast - Run quick tests first 2. Parallel execution - Run independent jobs concurrently 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills rmyndharis/deployment-pipeline-design