---|--------| | Dockerfile | Created | | docker-compose.yml | Created | | .env.example | Created |

Verification Results

Handoff to Next Gate

• Ready for Gate 2: YES

DevOps Setup (Gate 1)

Overview

This skill configures the development and deployment infrastructure:

• Creates or updates Dockerfile for the application

• Configures docker-compose.yml for local development

• Documents environment variables in .env.example

• Verifies the containerized application works

CRITICAL: Role Clarification

This skill ORCHESTRATES. DevOps Agent IMPLEMENTS.

Who Responsibility

This Skill Gather requirements, prepare prompts, validate outputs

DevOps Agent Create Dockerfile, docker-compose, .env.example, verify

Step 1: Validate Input

<verify_before_proceed>

• unit_id exists

• language is valid (go|typescript|python)

• service_type is valid (api|worker|batch|cli)

• implementation_files is not empty </verify_before_proceed>

REQUIRED INPUT (from ring:dev-cycle orchestrator):

• unit_id: [task/subtask being containerized]
• language: [go|typescript|python]
• service_type: [api|worker|batch|cli]
• implementation_files: [files from Gate 0]

OPTIONAL INPUT:

• gate0_handoff: [full Gate 0 output]
• new_dependencies: [deps added in Gate 0]
• new_env_vars: [env vars needed]
• new_services: [postgres, redis, etc.]
• existing_dockerfile: [true/false]
• existing_compose: [true/false]

if any REQUIRED input is missing: → STOP and report: "Missing required input: [field]" → Return to orchestrator with error

Step 2: Analyze DevOps Requirements

1. Check existing files:

   • Dockerfile: [EXISTS/MISSING]
   • docker-compose.yml: [EXISTS/MISSING]
   • .env.example: [EXISTS/MISSING]

2. Determine actions needed:

   • Dockerfile: CREATE / UPDATE / NONE
   • docker-compose.yml: CREATE / UPDATE / NONE
   • .env.example: CREATE / UPDATE / NONE

3. Identify services needed:

   • From new_services input
   • From language (Go → alpine base, TS → node base)
   • From service_type (api → expose port, worker → no port)

Step 3: Initialize DevOps State

devops_state = { unit_id: [from input], dockerfile_action: "pending", compose_action: "pending", env_action: "pending", services: [], verification: { build: null, startup: null, health: null }, iterations: 0, max_iterations: 3 }

Step 4: Dispatch DevOps Agent

<dispatch_required agent="ring:devops-engineer"> Create/update Dockerfile, docker-compose.yml, and .env.example for containerization. </dispatch_required>

Task: subagent_type: "ring:devops-engineer" description: "Create/update DevOps artifacts for [unit_id]" prompt: | ⛔ MANDATORY: Create all DevOps Artifacts

## Input Context
- **Unit ID:** [unit_id]
- **Language:** [language]
- **Service Type:** [service_type]
- **Implementation Files:** [implementation_files]
- **New Dependencies:** [new_dependencies or "None"]
- **New Environment Variables:** [new_env_vars or "None"]
- **New Services Needed:** [new_services or "None"]

## Existing Files
- Dockerfile: [EXISTS/MISSING]
- docker-compose.yml: [EXISTS/MISSING]
- .env.example: [EXISTS/MISSING]

## Standards Reference
WebFetch: https://raw.githubusercontent.com/LerianStudio/ring/main/dev-team/docs/standards/devops.md

You MUST implement all sections from devops.md.

## Requirements

### Dockerfile
- Multi-stage build (builder → production)
- Non-root USER (appuser)
- Specific versions (no :latest)
- HEALTHCHECK instruction
- Layer caching optimization

### docker-compose.yml
- Version: 3.8
- App service with build context
- Database/cache services as needed
- Named volumes for persistence
- Health checks with depends_on conditions
- Network: app-network (bridge)

### .env.example
- all variables with placeholders
- Comments explaining each
- Grouped by service
- Required vs optional marked
- **MANDATORY: Multi-tenant variables** (for ALL services):
  ```
  # Multi-tenant configuration (MANDATORY)
  MULTI_TENANT_ENABLED=false
  MULTI_TENANT_URL=
  MULTI_TENANT_ENVIRONMENT=staging
  ```

## Required Output Format

### Standards Coverage Table
| # | Section (from devops.md) | Status | Evidence |
|---|--------------------------|--------|----------|
| 1 | Containers | ✅/❌ | Dockerfile:[line] |
| 2 | Docker Compose | ✅/❌ | docker-compose.yml:[line] |
| 3 | Environment | ✅/❌ | .env.example:[line] |
| 4 | Health Checks | ✅/❌ | [file:line] |

### Files Created/Updated
| File | Action | Key Changes |
|------|--------|-------------|
| Dockerfile | Created/Updated | [summary] |
| docker-compose.yml | Created/Updated | [summary] |
| .env.example | Created/Updated | [summary] |

### Verification Commands

<verify_before_proceed>
- docker-compose build succeeds
- docker-compose up -d starts all services
- docker-compose ps shows healthy status
- docker-compose logs shows JSON format
</verify_before_proceed>

Execute these and report results:
1. `docker-compose build` → [PASS/FAIL]
2. `docker-compose up -d` → [PASS/FAIL]
3. `docker-compose ps` → [all healthy?]
4. `docker-compose logs app | head -5` → [JSON logs?]

### Compliance Summary
- **all STANDARDS MET:** ✅ YES / ❌ no
- **If no, what's missing:** [list sections]

Step 5: Validate Agent Output

Parse agent output:

1. Extract Standards Coverage Table
2. Extract Files Created/Updated
3. Extract Verification results

if "all STANDARDS MET: ✅ YES" and all verifications PASS: → devops_state.dockerfile_action = [from table] → devops_state.compose_action = [from table] → devops_state.env_action = [from table] → devops_state.verification = {build: PASS, startup: PASS, health: PASS} → Proceed to Step 7

if any section has ❌ or any verification FAIL: → devops_state.iterations += 1 → if iterations >= max_iterations: Go to Step 8 (Escalate) → Re-dispatch agent with specific failures

Step 6: Re-Dispatch for Fixes (if needed)

Task: subagent_type: "ring:devops-engineer" description: "Fix DevOps issues for [unit_id]" prompt: | ⛔ FIX REQUIRED - DevOps Standards Not Met

## Issues Found
[list ❌ sections and FAIL verifications]

## Standards Reference
WebFetch: https://raw.githubusercontent.com/LerianStudio/ring/main/dev-team/docs/standards/devops.md

Fix all issues and re-run verification commands.
Return updated Standards Coverage Table with all ✅.

After fix → Go back to Step 5

Step 7: Prepare Success Output

Generate skill output:

DevOps Summary

Status: PASS Unit ID: [unit_id] Iterations: [devops_state.iterations]

Files Changed

Services Configured

Verification Results

Handoff to Next Gate

• DevOps status: COMPLETE
• Services: [list]
• Env vars: [count] documented
• Verification: all PASS
• Ready for Gate 2 (SRE): YES

Step 8: Escalate - Max Iterations Reached

Generate skill output:

DevOps Summary

Status: FAIL Unit ID: [unit_id] Iterations: [max_iterations] (MAX REACHED)

Files Changed

[list what was created/updated]

Issues Remaining

[list unresolved issues]

Verification Results

[list PASS/FAIL for each check]

Handoff to Next Gate

• DevOps status: FAILED
• Ready for Gate 2: no
• Action Required: User must manually resolve issues

⛔ ESCALATION: Max iterations (3) reached. User intervention required.

Severity Calibration

Severity Criteria Examples

CRITICAL Security risk, deployment blocked :latest tags, secrets in image, root user, missing HEALTHCHECK

HIGH Build fails, services broken docker-compose build fails, services don't start, no health checks

MEDIUM Configuration gaps, optimization issues Missing layer caching, no named volumes, incomplete .env.example

LOW Best practices, documentation Missing comments in Dockerfile, suboptimal ordering

Report all severities. CRITICAL = immediate fix. HIGH = fix before gate pass. MEDIUM = fix in iteration. LOW = document.

Pressure Resistance

See shared-patterns/shared-pressure-resistance.md for universal pressure scenarios.

User Says Your Response

"Skip Docker, runs fine locally" "Docker ensures consistency. Dispatching ring:devops-engineer now."

"Demo tomorrow, no time" "Docker takes 30 min. Better than environment crash during demo."

"We'll containerize later" "Later = never. Containerizing now."

Anti-Rationalization Table

See shared-patterns/shared-anti-rationalization.md for universal anti-rationalizations.

Gate 1-Specific Anti-Rationalizations

Rationalization Why It's WRONG Required Action

"Works fine locally" Your machine ≠ production Containerize for consistency

"Docker is overkill" Docker is baseline, not overkill Create Dockerfile

"Just need docker run" docker-compose is reproducible Use docker-compose

"Lambda doesn't need Docker" SAM uses Docker locally Use SAM containers

Execution Report Format

DevOps Summary

Status: [PASS|FAIL|PARTIAL] Unit ID: [unit_id] Duration: [Xm Ys] Iterations: [N]

Files Changed

Services Configured

Verification Results

Handoff to Next Gate

• DevOps status: [COMPLETE|PARTIAL|FAILED]
• Ready for Gate 2: [YES|no]