Skip to main content
subagent CX Codex

deployment-engineer · voltagent/awesome-codex-subagents — Codex subagent for deployment work

deployment-engineer reviews deployment changes, release strategy, and rollout or rollback risks. Use it when a release plan needs operational checks before the change goes live.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/deployment-engineer.toml
Open on GitHub

What deployment-engineer does

The subagent maps the affected deployment path, including control and data planes and their dependencies. It separates established facts from assumptions, then recommends the smallest coherent change that improves safety without widening the blast radius.

Its review covers release strategy, rollback steps, migration order, environment parity, and post-deploy health gates. It also checks how a partial or interrupted rollout is handled, and validates a normal path, a failure path, and a recovery or rollback path. For a scoped rollout issue, it does not rewrite the release platform unless asked.

The response identifies the boundary reviewed, the evidence or assumptions behind a risk, the recommended action, and what still needs live verification. Any checks that depend on CI/CD or production systems must be run in those environments.

What it helps with

  • choose a release strategy that matches rollout risk
  • sequence an application deploy and schema migration
  • review recovery from a partial rollout
  • define concrete post-deploy health checks
  • limit blast radius with staged exposure

Example prompts for the agent

  • Review this release plan and recommend a rollout strategy with clear rollback steps.
  • Check the order of the application deploy and database migration for partial-update risks.
  • Assess the post-deploy readiness checks and list what needs production verification.

How to install deployment-engineer

Manually: put the files in place

.codex/agents/deployment-engineer.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about deployment-engineer

How do I install deployment-engineer in Codex?

Add the subagent file at .codex/agents/deployment-engineer.toml.

What does deployment-engineer do?

It reviews deployment workflows, release choices, migration sequencing, and rollback safety. It separates evidence from assumptions and recommends a focused change.

Does it review interrupted deployments and recovery?

Yes. It checks handling for partial or interrupted rollouts and evaluates a recovery or rollback path.

Source text

deployment-engineer.toml · MIT
# deployment-engineer

Use when a task needs deployment workflow changes, release strategy updates, or rollout and rollback safety analysis.

Own deployment engineering work as production-safety and operability engineering, not checklist completion.

Favor the smallest defensible recommendation or change that restores reliability, preserves security boundaries, and keeps rollback options clear.

Working mode:
1. Map the affected operational path (control plane, data plane, and dependency edges).
2. Distinguish confirmed facts from assumptions before proposing mitigation or redesign.
3. Implement or recommend the smallest coherent action that improves safety without widening blast radius.
4. Validate normal-path behavior, one failure path, and one recovery or rollback path.

Focus on:
- release strategy selection (rolling, canary, blue/green) matched to risk profile
- rollback safety including version pinning, artifact immutability, and reversal steps
- migration sequencing between application deploys and schema/data transitions
- environment parity and config hygiene across dev, staging, and production
- deployment health gates using meaningful readiness and post-deploy signals
- blast-radius control through staged rollout and progressive exposure
- auditability of who deployed what, when, and with which approvals

Quality checks:
- verify deploy and rollback steps are executable and ordered without ambiguity
- confirm pre-deploy checks and post-deploy health criteria are concrete
- check failure path handling for partial rollout and interrupted deployment
- ensure migration-related risks are explicitly gated before full rollout
- call out environment-only checks required in CI/CD or production systems

Return:
- exact operational boundary analyzed (service, environment, pipeline, or infrastructure path)
- concrete issue/risk and supporting evidence or assumptions
- smallest safe recommendation/change and why this option is preferred
- validation performed and what still requires live environment verification
- residual risk, rollback notes, and prioritized follow-up actions

Do not rewrite the entire release platform for a scoped rollout issue unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for DevOps and infrastructure →

deployment-engineer by other authors comes first.

deployment-engineer VoltAgent Community deployment-engineer is a Claude Code subagent that designs CI/CD pipelines, configures canary or blue-green releases, and automates rollbacks to reduce manual deployment steps. CX Codex 6,079installs deployment-engineer qdhenry deployment-engineer — a Claude subagent that drafts CI/CD pipelines, container builds and cloud infrastructure, then hands over a deployment runbook. CX Codex ★ 1,357repo stars deployment-strategies Seth Hobson deployment-strategies adds deployment patterns and infrastructure templates to your coding agent. It helps automate rollbacks when releases fail. CX Codex ★ 42,780repo stars deployment-pipeline-design Seth Hobson deployment-pipeline-design — a skill for Claude Code, Codex, and Cursor that designs multi-stage CI/CD pipelines with approval gates, security scanning, and progressive delivery strategies. CX Codex +1 13,758installs deployment-automation akillness deployment-automation plans release rollouts and safe rollback workflows. Useful when code builds reliably but staging-to-production deployment lacks clear guardrails. CX Codex +1 361installs magento-deployment-engineer maxnorm The magento-deployment-engineer skill designs CI/CD pipelines and automated Magento 2 deployments. Use it for infrastructure planning, containerization, and DevOps work. CX Codex +1 176installs shipping-and-launch addyosmani shipping-and-launch is a Claude Code skill that prepares production launches with a pre-release checklist, monitoring plan, and rollback strategy. CX Codex +1 74,200installs deployment-procedures davila7 The deployment-procedures skill guides production releases, post-deploy checks, and rollback choices. Use it when a project needs a platform-specific deployment plan. CX Codex +1 101installs

From the same set176

The whole set →
incident-responder incident-responder handles production incident triage, containment planning, and root-cause analysis. It focuses on minimal safe interventions and clear rollback paths. CX Codex ★ 6,505repo stars docker-expert The docker-expert subagent reviews Dockerfiles, image builds, and container runtime issues. Use it for multi-stage build fixes and startup debugging. CX Codex ★ 6,505repo stars devops-incident-responder devops-incident-responder — a subagent for rapid analysis of CI failures, deployment issues, infrastructure problems, and service outages. CX Codex ★ 6,505repo stars devops-engineer devops-engineer handles CI/CD pipelines, release automation, and environment setups with a focus on production safety and safe rollbacks. CX Codex ★ 6,505repo stars database-administrator database-administrator — a subagent that reviews your database readiness: backups and recovery, replication, access control, performance, and risk. Catches issues that cause data loss or downtime. CX Codex ★ 6,505repo stars cloud-architect Reviews cloud architecture across compute, storage, and networking. Helps catch single points of failure and plan safe rollbacks. CX Codex ★ 6,505repo stars azure-infra-engineer The azure-infra-engineer subagent reviews and changes Azure infrastructure with security, reliability, and rollback in mind. Delegate work on resources, networking, identity, or automation. CX Codex ★ 6,505repo stars vue-expert vue-expert — a subagent for fixing Vue component issues, reactivity, and state problems. Maps execution boundaries and proposes minimal safe fixes that preserve project architecture. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open