agent team orchestration

AI Community

Skill notes

Quick Start: Minimal 2-Agent Team

A builder and a reviewer. The simplest useful team.

3. Add a Reviewer

That's the core loop. Everything below scales this pattern.

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)

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

Handoffs

When work passes between agents, the handoff message includes: What was done — summary of changes/output Where artifacts are — exact file paths How to verify — test commands or acceptance criteria Known issues — anything incomplete or risky

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@LeoYeAI · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview agent-team-orchestration.preview
# Spawning without clear artifact output paths

Agent produces great work, but you can't find it. Always specify the exact output path in the spawn prompt. Use a shared artifacts directory with predictable structure.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.