Multi-Team Orchestration Template

Run a solo software team through one orchestrator with built-in planning, engineering, and validation roles.

This template is for developers who want the feel of a real software organization without manually coordinating multiple agents. You give one request to the orchestrator. The system routes work to the right leads and workers, keeps role boundaries intact, and returns one coordinated result.

Why This Exists

Most agent setups break down in one of two ways:

• one agent does everything and loses structure
• many agents exist, but the human has to coordinate all of them

This template takes a different approach:

• one operator-facing orchestrator
• clear team hierarchy
• scoped worker domains
• reusable prompts, expertise, and skills
• validation built into the workflow instead of added later

Team Model

The system models a small software company:

• Orchestrator
• Planning Lead
• Engineering Lead
• Validation Lead
• Product Manager
• UX Researcher
• Backend Developer
• Frontend Developer
• QA Engineer
• Security Reviewer

In practice, that means:

• planning thinks before implementation
• engineering builds within domain boundaries
• validation reviews quality and risk before work is considered complete

How It Works

1. The user gives one request to the orchestrator.
2. The orchestrator delegates to the relevant leads.
3. Leads coordinate workers within their own team scope.
4. Workers operate with constrained read/write domains.
5. Validation checks the result before the orchestrator returns a final answer.

What Makes This Different

• Role-based orchestration instead of one general-purpose agent
• Durable expertise files for each role
• Reusable skill modules injected into prompts
• Guarded file access based on team responsibilities
• One reusable framework that can be copied into new project repos

Quick Start

cp .env.example .env
bun install
bun run dev

Current runtime env:

• ANTHROPIC_API_KEY

Demo

What you type:

Build a Postman-style request builder with collections, environments, and response history.

What the system does:

• planning defines the feature shape
• engineering splits backend and frontend work
• validation reviews QA and security impact
• orchestrator returns one coordinated response

You can use the screenshots in ui-img/ for the GitHub repo page and for launch posts.

Template Boundaries

This repo is intentionally a framework template, not a project output repo.

Tracked in Git:

• src/
• .pi/multi-team-config.yaml
• .pi/multi-team/agents/
• .pi/multi-team/expertise/
• .pi/multi-team/skills/
• .env.example
• idea.md

Ignored from Git:

• .pi/auth.json
• .pi/models.json
• .pi/multi-team/sessions/
• .env
• ai_docs/
• project-specific apps/
• project-specific specs/

Using This Template

1. Push this repository to GitHub.
2. Mark it as a Template Repository.
3. Create a new repo from this template whenever you start a new build.
4. Add your project-specific apps/ and specs/ in the derived repo.
5. Adjust .pi/multi-team-config.yaml if you want different models, commands, or domain rules.

Roadmap

• Better onboarding for first-time users
• Cleaner example project walkthroughs
• More built-in team configurations
• Better visibility into delegation and review flow

Core Idea

One solo developer. One interface. One orchestrator. A full software company behind it.