Agent skill · bighardperson
agent-team-orchestration
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.
What it needs
About 3k tokens when loaded.
What this skill does
Agent Team Orchestration Production playbook for running multi-agent teams with clear roles, structured task flow, and quality gates. Quick Start: Minimal 2-Agent Team A builder and a reviewer. The simplest useful team. 1. Define Roles 2. Spawn a Task 3. Add a Reviewer That's the core loop. Everything below scales this pattern. Core Concepts Roles Every agent has one primary role. Overlap causes confusion. Role Purpose Model guidance ------ --------- --------------- Orchestrator Route work, track state, make priority calls High-reasoning model (handles judgment) Builder Produce artifacts — code, docs, configs Can use cost-effective models for mechanical work Reviewer Verify quality, push back on gaps High-reasoning model (catches what builders miss) Ops Cron jobs, standups, health checks, dispatching Cheapest model that's reliable → Read references/team-setup.md when defining a new team or adding agents. Task States Every task moves through a defined lifecycle: Rules: Orchestrator owns state transitions — don't rely on agents to update their own status Every transition gets a comment (who, what, why) Failed is a valid end state — capture why and move on → Read references/task-lifecycle.md when designing task flows or debugging stuck tasks. Handoffs When work passes between agents, the handoff message includes: 1. What was done — summary of changes/output 2. Where artifacts are — exact file paths 3. How to verify — test commands or acceptance criteria 4. Known issues — anything incomplete or risky 5. What's next — clear next action for the receiving agent Bad handoff: "Done, check the files." Good handoff: "Built auth module at /shared/artifacts/auth/. Run npm test auth to verify. Known issue: rate limiting not implemented yet. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills bighardperson/Agent Team Orchestration