DevOps & Deployment Pro

What it does

DevOps & Deployment Pro is a Cursor agent playbook named devops-engineer. AgenticKit installs it so a session can adopt this role instead of acting as a generic coding assistant.

The devops-engineer agent automates your continuous integration and deployment workflows. It writes secure multi-stage Docker builds, configures GitHub Actions matrix tests, sets up preview environments, and configures edge routing.

Configures Docker containers, Vercel/AWS hosting, CI/CD pipelines, and Nginx. DevOps engineer for Cursor that crafts multi-stage Dockerfiles, automates GitHub Actions pipelines, and configures production infrastructure.

Why it exists

A pile of agent files is not a team. devops-engineer exists so one job, devops & deployment pro, has a written brief, required skills, and a stop condition.

It ships in the Engineering Kit. Skills it must read: GitHub Actions CI/CD Pipeline Automation; Multi-Stage Docker & Container Deployments; Terraform Infrastructure as Code (IaC); Observability, Telemetry & SRE Monitoring. Commands that adopt this role: /ci-pipeline: GitHub Actions CI/CD Pipeline Generator; /dockerize: Docker & Containerization Configurator; /cloud-infra: Cloud Infrastructure as Code (Terraform / IaC).

When to use it

• Setting up zero-friction CI/CD deployment pipelines
• Containerizing full-stack applications with Docker
• Configuring staging environments and branch previews

When not to use it

• Do not ask devops-engineer to do a different role's job. If you need a launch post, switch agents.
• Do not keep the same chat after this agent has finished its artifact. Start a reviewer in a new thread.
• Do not invoke every agent in the kit for a small change.

Example workflow

1. Install the Engineering Kit so .cursor/agents/devops-engineer is on disk.
2. Run /ci-pipeline: GitHub Actions CI/CD Pipeline Generator, or start a chat and tell Cursor to adopt the devops-engineer role.
3. The agent should read: GitHub Actions CI/CD Pipeline Automation; Multi-Stage Docker & Container Deployments; Terraform Infrastructure as Code (IaC); Observability, Telemetry & SRE Monitoring.
4. It produces the artifact for this role only, then stops.
5. A different agent or you review. Same-chat self-review is not a review.

Example usage

Example: "You are devops-engineer. Setting up zero-friction CI/CD deployment pipelines. Read github-actions before you edit."

Or let the pipeline invoke it: /ci-pipeline: GitHub Actions CI/CD Pipeline Generator.

Capabilities you should actually see: Multi-stage Dockerfile creation and image size minimization

Example output

• devops-engineer should leave files or a written verdict, not a vibe check. Multi-stage Dockerfile creation and image size minimization GitHub Actions workflows for automated test, build, and deploy
• Engineering agents should touch the slice they were given (schema, route, test, or review note) and nothing else.

Best practices

• Multi-stage Dockerfile creation and image size minimization
• GitHub Actions workflows for automated test, build, and deploy
• Vercel, AWS ECS, Fly.io, and Railway production deployments
• Environment variable management and build-time optimization
• One role per chat unless a command is explicitly orchestrating a sequence.

Common mistakes

• Using devops-engineer as a synonym for 'the Cursor agent'. It is a brief, not the product.
• Skipping the required skills and hoping the role name is enough.
• Letting the writer approve its own PR.
• Invoking this agent and three unrelated ones in the same prompt.