advanced6 agentsMixedcurrent

Full Engineering Org

A larger setup for planning, implementation, review, QA, and operations when one repo has multiple parallel streams.

Tested against paperclip 0.9

paperclip-company.yaml

company:
  name: "Full Engineering Org"
  mission: "Ship software changes safely across one active product"

agents:
  - name: "Product Lead"
    adapter: claude-local
    role: "product lead"
    reports_to: board
    budget: "$20/month"

  - name: "Backend Engineer"
    adapter: codex
    role: "backend engineer"
    reports_to: Product Lead
    budget: "$30/month"

  - name: "Frontend Engineer"
    adapter: codex
    role: "frontend engineer"
    reports_to: Product Lead
    budget: "$30/month"

  - name: "Reviewer"
    adapter: claude-local
    role: "code reviewer"
    reports_to: Product Lead
    budget: "$15/month"

  - name: "QA"
    adapter: claude-local
    role: "qa analyst"
    reports_to: Product Lead
    budget: "$15/month"

  - name: "Ops"
    adapter: http
    role: "deployment operator"
    reports_to: Product Lead
    budget: "$10/month"

Prerequisites

A codebase with strong ownership boundaries
Test and deploy steps that can be verified automatically
Clear escalation rules for risky production work

Use this template

Start from Startup Trio first if you have never run a multi-agent company.
Add review and operations only when parallel work creates real coordination cost.
Keep shared write access narrow to avoid merge conflicts and noisy failures.

Why this template works

It separates delivery into real stages instead of pretending one giant engineer agent can safely do everything.

Warning

This template is only useful if your repo and deployment flow already have clear boundaries. If not, start smaller.