agent-team-design

$npx mdskill add agentlas-ai/Agentlas-OS/agent-team-design

Design multi-agent teams with role boundaries and handoff flows.

  • Designs multi-agent teams from user job and runtime requirements.
  • Uses visible agents folder, skills directory, and company blueprint.
  • Starts with one agent, adds roles only when needed for routing or policy.
  • Outputs role list, handoff direction, memory, policy, and eval owners.

SKILL.md

.github/skills/agent-team-designView on GitHub ↗
---
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

1. Define the user job and target runtime.
2. Start with one agent. Add team roles only when routing, memory, review,
   policy, or parallel ownership is useful.
3. 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`
4. Add `skills/<capability>/SKILL.md` for reusable procedures.
5. Add `.agentlas/company-blueprint.json` for topology.

## Output

Return the role list, handoff direction, memory owner, policy owner, and eval
owner.

More from agentlas-ai/Agentlas-OS

SkillDescription
agentlas-auto-activationUse when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
agentlas-core-engine-meta-agentUse when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into Agentlas architecture. Make sure to use this for /meta-agent requests.
agentlas-packagingUse when converting, repairing, or packaging an existing local or external agent/team into Agentlas architecture for local install, Agentlas import, Codex plugin use, Claude adapter use, or open-source release.
agentlas-security-scanUse when an agent folder must pass the Agentlas Cloud 2-stage security scan (static rules + BYOK LLM judgment) before private sync or public publish, or when asked to run/interpret `hephaestus security scan`.
clarify-question-loopUse when a meta-agent request is too ambiguous to safely generate, package, publish, or adapt without one to five targeted questions.
hephaestus-buildUse when the user types /prompts:hep-build, mentions @Hephaestus for build work, asks to create a single Agentlas agent, create a multi-agent team, or package an existing local/external agent into Agentlas architecture.
hephaestus-cloudUse when the user types /hep-cloud or asks to staff from THEIR OWN Agentlas cloud packages only. Cloud is one exact source scope; Network means Local + owner Cloud + public Hub.
hephaestus-networkUse when the user types /hep-network, mentions @Hephaestus, or asks Agentlas to staff a task from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM is the temporary orchestrator.
hephaestus-stormUse when the user types /hep-storm, says @Hephaestus storm <goal>, or asks to drive a goal to verified completion through a force-robust Stormbreaker loop. Stormbreaker routes the goal to real Agentlas specialists, materializes a dependency-ordered pipeline fabric, and runs each work packet as a verifier-first hardened loop that does not stall, run away, or claim false success. Use it for loop-worthy work — apps, sites, agents, automations, debugging, multi-step research, data/report generation. Trivial questions are answered directly, not stormed.
install-verificationUse when verifying that a generated agent package can be installed, discovered by runtimes, and checked without private dependencies.