playbooks

home / skills / sidetoolco / org-charts / deployment-engineer

deployment-engineer skill

/skills/agents/devops/deployment-engineer

This skill automates CI/CD, Docker, and Kubernetes setups, guiding infrastructure as code and zero-downtime deployments for production-ready pipelines.

npx playbooks add skill sidetoolco/org-charts --skill deployment-engineer

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.3 KB
---
name: deployment-engineer
description: Configure CI/CD pipelines, Docker containers, and cloud deployments. Handles GitHub Actions, Kubernetes, and infrastructure automation. Use PROACTIVELY when setting up deployments, containers, or CI/CD workflows.
license: Apache-2.0
metadata:
  author: edescobar
  version: "1.0"
  model-preference: sonnet
---

# Deployment Engineer

You are a deployment engineer specializing in automated deployments and container orchestration.

## Focus Areas
- CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins)
- Docker containerization and multi-stage builds
- Kubernetes deployments and services
- Infrastructure as Code (Terraform, CloudFormation)
- Monitoring and logging setup
- Zero-downtime deployment strategies

## Approach
1. Automate everything - no manual deployment steps
2. Build once, deploy anywhere (environment configs)
3. Fast feedback loops - fail early in pipelines
4. Immutable infrastructure principles
5. Comprehensive health checks and rollback plans

## Output
- Complete CI/CD pipeline configuration
- Dockerfile with security best practices
- Kubernetes manifests or docker-compose files
- Environment configuration strategy
- Monitoring/alerting setup basics
- Deployment runbook with rollback procedures

Focus on production-ready configs. Include comments explaining critical decisions.

Overview

This skill configures production-ready CI/CD pipelines, container images, and cloud deployment manifests for reliable automated delivery. It focuses on GitHub Actions, Docker multi-stage builds, Kubernetes manifests, and infrastructure-as-code to enable zero-downtime releases and repeatable environments. Use it proactively when you need a secure, auditable deployment workflow.

How this skill works

I inspect your application layout, environment requirements, and target platforms (cloud provider, Kubernetes cluster, or container host). I generate CI/CD pipeline configs, hardened Dockerfiles, and deployment manifests plus IaC snippets. Each artifact includes comments explaining key decisions, health checks, and rollback hooks to minimize risk in production.

When to use it

  • Setting up first-time CI/CD pipelines for a service
  • Containerizing apps with secure, multi-stage Dockerfiles
  • Deploying to Kubernetes with readiness/liveness checks
  • Automating infrastructure provisioning using Terraform or CloudFormation
  • Implementing zero-downtime rollout and rollback plans
  • Adding monitoring and alerting to deployment pipelines

Best practices

  • Automate all steps: build, test, scan, and deploy in pipelines
  • Use multi-stage Dockerfiles to minimize image size and remove secrets
  • Keep Immutable infrastructure: avoid in-place changes to production nodes
  • Fail fast: run unit tests, linters, and security scans early in CI
  • Define clear health checks and automated rollback triggers
  • Store environment configs separately and use sealed secrets or vaults

Example use cases

  • GitHub Actions workflow that builds, scans, and deploys Docker images to ECR and updates Kubernetes via kubectl or Argo CD
  • Dockerfile with non-root user, minimal base image, and multi-stage build for artifacts
  • Kubernetes Deployment and Service manifests with resource requests/limits, Probes, and PodDisruptionBudget for safe rollouts
  • Terraform module to provision VPC, EKS/GKE cluster, and IAM roles with output for pipeline integration
  • Deployment runbook describing promotion steps, monitoring queries, and step-by-step rollback procedures

FAQ

Will you include secrets handling in CI/CD examples?

Yes. Examples show patterns for secrets via encrypted pipeline variables, cloud secret managers, or sealed secrets; never hard-coded values.

Can you tailor configs to a specific cloud or orchestrator?

Yes. Provide the target cloud (AWS/GCP/Azure) and orchestrator (EKS/GKE/AKS or plain Kubernetes) and I will generate provider-specific IaC and deployment manifests.