Coordinate sub-agents to monitor PRs and fix prod bugs
A Cursor Projects coordinator agent delegates to sub-agents, watches new PRs and production bugs, spins up agents to fix issues, and surfaces questions to the user.
Cursor agents create Terraform, k8s manifests and CI, validate them and open a draft PR; one cleanup run wrongly deleted Terraform files.
Cursor agents create Terraform, k8s manifests and CI, validate them and open a draft PR; one cleanup run wrongly deleted Terraform files.
A task file in the repo, run with a service name and team name, drives the agent. It first checks GitHub, the cluster and Terraform state for conflicts. It then writes the Terraform service file, the Kubernetes Deployment, Service and HPA, and a CI workflow with a Trivy scan. It runs terraform validate and kubectl dry-run, then opens a draft PR with a checklist. A senior engineer reviews before merge.
The article describes a new engineer producing convention-compliant files this way, with no timing stated for this run. Separately, a vague prompt to clean up unused resources deleted 14 files, three of them Terraform files still managing state. A checkpoint rollback fixed it.
Replace vague prompts like cleanup with precise report-only tasks. Reviewers who skimmed let a cpu=10m limit through, so keep PRs small and use checkpoints.
Scaffold a new service called [service name] including Terraform, Kubernetes manifests, and CI config, validating each file as you go. Open a draft pull request with the changes, but show me exactly what will be created or deleted before running any cleanup or deletion commands.
A Cursor Projects coordinator agent delegates to sub-agents, watches new PRs and production bugs, spins up agents to fix issues, and surfaces questions to the user.
Ran a Cursor agent continuously for 24 hours to build a project management tool; the app fully works but is not production ready.
The author had ChatGPT take the Session Buddy extension source from Chrome, port it to Safari and install it, taking about 20 minutes.