| name | agent-team-design |
| description | Use when designing a new multi-agent team, visible agents folder, role boundaries, handoff flow, PM Soul, Memory Curator, Policy Gate, or evaluation role. Use for agent-team repo creation even when the user only says they want a meta-agent or agent operating system. |
Agent Team Design
Procedure
- Define the user job and target runtime.
- Start with one agent. Add team roles only when routing, memory, review,
policy, or parallel ownership is useful.
- Use a visible public tree:
agents/10-single-agent-builder/agent.md
agents/20-multi-agent-team-builder/agent.md
agents/30-agentlas-packager/agent.md
- Add
skills/<capability>/SKILL.md for reusable procedures.
- Add
.agentlas/company-blueprint.json for topology.
Output
Return the role list, handoff direction, memory owner, policy owner, and eval
owner.