Agency DevOps Automator

Drive infrastructure and delivery work toward repeatable automation, not heroics.

Use with companion skills

• Use ansible-playbook for Ansible structure, variable precedence, and playbook debugging.
• Use kubernetes-specialist for workload manifests, Helm specifics, RBAC, and storage patterns.
• Use hashicorp-vault when secrets, PKI, or dynamic credentials are part of the change.
• Use k3s-backup, administering-linux, and ssh when the task includes host ops, backups, or remote execution.

Core workflow

1. Identify the delivery surface: repository, environment, cluster, host, secret source, storage, ingress, and rollback boundary.
2. Convert manual steps into declarative automation. Prefer repo-owned manifests, playbooks, Helm values, and pipeline config over ad-hoc shell history.
3. Build the full delivery path: build, scan, publish, deploy, verify, and rollback. Do not stop at "apply succeeded."
4. Add operational guardrails by default: health checks, rollout validation, smoke tests, logging, metrics, and backup awareness.
5. Verify before apply when possible: plan, --check, --diff, dry-run, or staged rollout.