Skip to content
Get packs

Deployment Pipeline Design

Design multi-stage CI/CD pipelines with approval gates, canary rollouts and safe rollbacks

Source Download skill
Repository
wshobson/agents
Stars
42,095
Licence
MIT
Files
3 files

What it does

When installed, the agent gets structured guidance for planning how software moves from development to staging to production safely. It can propose pipeline stages, approval gates, canary or blue-green rollout strategies, health checks, and rollback plans, and it can help debug cases where a deployment gate fails or a canary never promotes. The skill is documentation-style guidance that shapes the agent's advice and sample configuration files; it does not itself deploy anything.

Great for

  • Engineers designing or migrating a CI/CD pipeline for a service on Kubernetes, ECS, VMs or serverless platforms
  • Teams adding approval gates, security scans or multi-environment promotion to an existing pipeline
  • Developers troubleshooting a canary rollout that stalls or a production job that never starts

Skip it if

  • People who need a ready-to-run pipeline for one specific CI tool: sibling skills such as github-actions-templates or gitlab-ci-patterns are more specific, and the agent's output here should be reviewed before use
  • Production changes made without review: the sample YAML, Dockerfile and migration snippets are illustrative and must be checked against your own environment, since mistakes can cause outages or data problems

Try asking

  • “Design a three-stage pipeline (dev, staging, prod) with manual approval before production for a containerized Node.js service on Kubernetes”
  • “Set up a canary rollout with Argo Rollouts that auto-promotes based on Prometheus error rates”
  • “Why does my GitHub Actions production deploy wait forever without notifying anyone?”
  • “Plan a database migration strategy so we can roll back application code safely”
Step-by-step guide: how to use Deployment Pipeline DesignInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 3 original files, the MIT licence and an attribution note.

    deployment-pipeline-design.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip deployment-pipeline-design.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip deployment-pipeline-design.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Describe your deployment target, number of environments, acceptable downtime and monitoring stack up front so the advice is specific rather than generic
  • Treat generated YAML and scripts as drafts: test them in a non-production environment and verify metric names, environment names and reviewer settings against your real systems
  • Ask for the rollback plan and migration backward-compatibility rules alongside the pipeline design, since these are where deployments most often fail

What's inside

  • references/advanced-strategies.md
  • references/details.md
  • SKILL.md

Redistributed unmodified from wshobson/agents under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.