Menu
Use when admin requests creating a team, importing a team, managing team composition, adding/removing workers from a team, or delegating tasks to a Team Leader.
Use before any projectflow call or Team Leader workflow involving Project state, Project lifecycle, DAG planning, Loop planning, ready node checks, pause/resume/complete, project recovery, heartbeat project checks, or project-level result aggregation. Always use team-coordination first when the question is how to organize the work.
Use before any Leader taskflow call or task-level workflow involving delegating a ready DAG or Loop node, writing task meta/spec, checking a Worker task result, handling result statuses, task directory ownership, or Worker result contracts. Always use this skill when the request mentions delegate_task, check_task, task result.md, task spec.md, BLOCKED, REVISION_NEEDED, INTERRUPTED, SUCCESS, or assigning/delegating a Worker task.
Discover and install agent skills from the open ecosystem. Use when you encounter an unfamiliar domain, framework, or workflow that you lack specialized knowledge about, or when your coordinator suggests searching for skills before starting a task.
Discover and install agent skills from the open ecosystem. Use when you encounter an unfamiliar domain, framework, or workflow that you lack specialized knowledge about, or when your coordinator suggests searching for skills before starting a task.
Discover and install agent skills from the open ecosystem. Use when you encounter an unfamiliar domain, framework, or workflow that you lack specialized knowledge about, or when your coordinator suggests searching for skills before starting a task.
Use when admin requests hand-creating or resetting a Worker, starting/stopping a Worker, managing Worker skills, enabling peer mentions, or opening a QwenPaw console. Use hiclaw-find-worker only as a helper for Nacos-backed market import or when task assignment needs you to discover a suitable Worker.
| name | team-management |
| description | Use when admin requests creating a team, importing a team, managing team composition, adding/removing workers from a team, or delegating tasks to a Team Leader. |
A Team consists of 1 Team Leader + N Workers. The Team Leader is a special Worker with management skills that handles task decomposition and assignment within the team. Manager delegates tasks to Team Leaders, not directly to team workers.
# 1. Create team via hiclaw CLI
hiclaw create team \
--name <TEAM_NAME> \
--leader-name <LEADER_NAME> \
--leader-model <MODEL> \
--workers <w1>,<w2>
# 2. @mention the Leader in Leader Room to assign task
After creation, the Leader is online in the Leader Room (Manager + Global Admin + Leader). @mention the Leader there to delegate the task — the Leader will decompose it and coordinate with team workers in the Team Room.
Full workflow: read
references/create-team.md
If admin asks for CPU or memory requests/limits, use a YAML Team manifest with leader.resources and/or workers[].resources, then apply it with hiclaw apply -f. The simple hiclaw create team / hiclaw update team flags do not expose resource tuning. Changing member resources recreates the affected member container, so confirm the team is not mid-task.
--team-admin not specified--delegated-to-team — so heartbeat knows to check with Leader, not workersruntime: copaw for all team members — omit runtime from team creation| Admin wants to... | Read | Command |
|---|---|---|
| Create a new team | references/create-team.md | hiclaw create team |
| Understand team lifecycle | references/team-lifecycle.md | — |
| Delegate task to team | references/team-task-delegation.md | — |
| Add/remove worker from team | references/team-lifecycle.md | hiclaw get team |
| Delete a team's containers | references/team-lifecycle.md | scripts/lifecycle-worker.sh (per worker) |