jim0thy Team Orchestration
This skill provides a multi-agent orchestration system for complex coding tasks. It coordinates specialist agents — modeled after a well-run engineering team — to break down, plan, implement, and review work efficiently.
Agents
| Agent | Role | Best For |
|---|---|---|
| Tech Lead | Orchestrator | Coordinating complex multi-step tasks |
| Staff Engineer | Deep worker | Large implementations spanning 5+ files |
| Architect | Systems analyst | Debugging, architecture review, root-cause analysis |
| Navigator | Codebase expert | Finding code, explaining patterns, documentation |
| Scout | Fast search | Quick read-only codebase searches |
| Strategist | Planner | Creating implementation plans with phases |
| Advisor | Plan critic | Validating plans before execution |
How It Works
- All agents are registered as
customAgentsin the Copilot SDK session. - The SDK's built-in
tasktool enables agent-to-agent delegation. - All orchestration happens within a single premium request — subagent invocations are free.
- The Tech Lead coordinates specialists based on task complexity.
Usage
Via CLI (one-shot mode)
bun src/cli/index.ts "Refactor the authentication module to use JWT"
Programmatic
import { createAnvilSession } from "./src/cli/index.js";
const session = await createAnvilSession({
model: "claude-sonnet-4.6",
});
const response = await session.send("Add dark mode support");
await session.destroy();
Via TUI
The agents are automatically loaded when Anvil starts in TUI mode. Use:
Ctrl+Aor/agentsto see available agents/teamto enable orchestrated mode (Intake → Tech Lead → Specialists)/directto go back to single-agent mode
Single-Request Guarantee
The critical design constraint: 1 user message = 1 premium request. This is achieved because:
- Agents are SDK
customAgents, not separate API calls - The
tasktool delegates to subagents within the same request context - All tool calls, agent delegations, and follow-ups happen within a single
session.send()call - The request only completes when
session.idlefires
This means even a complex flow like:
User → Tech Lead → Strategist (plan) → Advisor (validate) → Staff Engineer (implement) → Reviewer (check) → User
...consumes exactly 1 premium request.