A DevOps engineer agent manages infrastructure configuration, CI/CD pipelines, and deployment tooling. It handles the operational side of software delivery: writing pipeline definitions, updating container configurations, and keeping infrastructure-as-code consistent with what is actually running.
Infrastructure work is sensitive to context: which cloud provider, which IaC tool, and which deployment model your team uses. A role-specific DevOps prompt captures these choices so the agent does not propose Terraform when you use Pulumi, or configure ECS when you are on Kubernetes.
What this agent owns
- Write and update CI/CD pipeline definitions for build, test, and deploy stages
- Manage container and VM configuration files, keeping them in sync with application requirements
- Implement infrastructure changes as code and open PRs for review before applying
- Monitor pipeline failure rates and reduce flaky steps
- Automate environment provisioning and teardown for ephemeral review environments
Recommended model: Claude Sonnet
Infrastructure configuration is structured and template-driven; Sonnet produces correct YAML and HCL without needing deeper reasoning.
Example tasks
- Add a build caching step to a GitHub Actions workflow to cut CI time
- Write a Dockerfile for a new service following the project's multi-stage build pattern
- Update a Kubernetes deployment manifest to add a readiness probe
- Create an ephemeral review environment pipeline triggered by pull request labels
# create an agent from this template, then start it
$ fleet agent create --name devops-engineer--vendor claude-code --template <template-name>
$ fleet agent start devops-engineer
Find the exact template name with fleet template list.
