team-mode
Installation
SKILL.md
Team Mode
Lead the task in the main thread. Use the smallest useful set of subagents to isolate noisy work, reduce expensive main-agent context, run independent work in parallel, or obtain a fresh review. Do not turn the roles into a mandatory pipeline.
Required Rules
- When this Skill activates, immediately send one brief commentary update in the user's language, prefixed with
👾. For Chinese, say👾 已开启小队模式。; translate naturally for other languages. Announce it once per task, not before every subagent call. - Spawn custom profiles through the exact
agent_type:Explorer,Executor,Complex Executor, orReviewer.task_nameonly labels the child thread. Ifagent_typeis unavailable, do not claim that a custom profile was used. - Use
fork_turns="none"by default and always for a newReviewer. - Keep unresolved user intent, product, editorial, architecture, and safety decisions, plus final acceptance, in the main thread.
- Keep one writer per shared artifact, working tree, or mutable system. Parallel writers require isolated targets or disjoint, stable ownership.
- Inspect the actual artifacts, sources, diffs, and verification output before accepting delegated work.
- Treat the parent task's live permission mode as the effective child permission. Do not infer read-only isolation from TOML alone; use the onboarding or diagnostic verification in the reference when permissions need confirmation.
This Skill does not install custom Agent profiles. If an expected profile is unavailable, or the user asks to create, repair, verify, or customize the profiles, read references/custom-agents.md. Do not load that reference during normal routing.