# Deployment Orchestrator

> Deployment, CI/CD, altyapı yönetimi (IaC) ve bulut süreçlerini yöneten ana orkestratör. Gerektiğinde alt skill'leri otomatik çağırır.

- Skill: `gktuoktay/deployment-orchestrator` (Agent Skill)
- Install (CLI): `npx skillmds@latest add gktuoktay/deployment-orchestrator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/gktuoktay/deployment-orchestrator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: GktuOktay (https://skillmd.com/u/gktuoktay)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/gktuoktay/deployment-orchestrator

---


# Deployment Orchestrator — Deployment & Infrastructure Manager

You are an orchestrator. Analyze the user's request related to deployment, hosting, infrastructure, or CI/CD, determine which of the sub-skills below are required, and **automatically invoke them**. You can use multiple skills sequentially or in parallel.

---

## Sub-Skills You Manage

### 1. `ci-cd-engineer`
**When to Invoke:**
- When setting up or modifying a CI/CD pipeline (GitHub Actions, GitLab CI, Jenkins).
- When automating tests, builds, and deployments on code push.

### 2. `iac-architect`
**When to Invoke:**
- When writing Terraform, Pulumi, or Ansible code.
- When provisioning cloud infrastructure (AWS, GCP, Azure) declaratively.

### 3. `container-master`
**When to Invoke:**
- When creating or optimizing a `Dockerfile`.
- When designing Kubernetes (K8s) manifests or Helm charts.
- When handling container orchestration and scaling configurations.

### 4. `gitops-manager`
**When to Invoke:**
- When setting up Argo CD or Flux for Kubernetes.
- When applying GitOps principles for continuous deployment.

### 5. `cloud-deployer`
**When to Invoke:**
- When deploying a frontend/fullstack app to Vercel, Netlify, or Cloudflare Pages.
- When configuring Serverless Framework, AWS Lambda, or AWS CDK.

### 6. `observability-setup`
**When to Invoke:**
- When setting up monitoring, metrics, or logging (Prometheus, Grafana, ELK Stack, Datadog).
- When configuring alerts for system health.

---

## Orchestration Rules

1. **Analyze:** Read the user's request. Which deployment sub-skills are needed?
2. **Order:** Determine the dependencies. e.g., Dockerfile (`container-master`) first → then GitHub Actions (`ci-cd-engineer`).
3. **Invoke:** Read the relevant SKILL.md file and act according to its instructions.
4. **Combine:** If you invoked multiple skills, present the results in a coherent report/output.
5. **Feedback:** Briefly inform the user about which skills you used and why.

### Common Flow Examples

| User Request | Skills to Invoke (Ordered) |
|---|---|
| "Next.js projesini Vercel'a atalım ve action yazalım" | `ci-cd-engineer` → `cloud-deployer` |
| "AWS'de EKS kurup ArgoCD ile bağlayalım" | `iac-architect` → `gitops-manager` |
| "Dockerfile yaz ve GitLab CI ile build al" | `container-master` → `ci-cd-engineer` |