DevOps Engineer

​

Purpose and Responsibilities

• Generate infra docs (e.g. hosting.md, cdn_caching.md, terraform.md, ci_cd.md, monitoring.md, secrets_management.md, gcp_deploy.md, ci_cd.md for mobile).
• Align with BackendDev on deployment and runtime needs.
• Coordinate with ToolManager for external services and export.

​

Input/Output

​

Input (from generateFileContentWithAgent)

• file, requirements, config, filePath, workflowContext, existingDeliverables — Same pattern as Product Manager.

​

Output

• Markdown string: deployment steps, env vars, CDN/caching, Terraform/IaC notes, CI/CD pipelines, monitoring, secrets. No fixed schema.

​

Prompt Engineering

• Agent system:
  "You are a DevOps Engineer agent. You create deployment configurations, CI/CD pipelines, and infrastructure code. Coordinate with BackendDev for deployment needs."
• Full prompt: Same generateFileContentWithAgent template; config.techStack.hosting and config.platform steer Vercel, Docker, AWS, GCP, Xcode Cloud, etc.
• Model: callOpenRouter(..., 'GROK', { temperature: 0.8 }).

​

File Assignment

• infra, deployment, or ci_cd

​

Examples

• infra/hosting.md, infra/cdn_caching.md (Website)
• infra/terraform.md, infra/ci_cd.md, infra/monitoring.md, infra/secrets_management.md (Web App)
• infra/ci_cd.md (iOS, Xcode Cloud)
• infra/gcp_deploy.md (Android, GCP)

​

Customization Options

• Agent system: Edit the DevOpsEngineer entry in agentSystemPrompts in lib/platform-templates.ts.
• Assignment: Map paths like k8s/, docker/ to DevOpsEngineer in getAgentForFile.
• Platform templates: Add or change infra/ files in folderStructure for each platform.