Agent Team Workflows
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill coherently coordinates multiple Claude teammates, but users should be comfortable enabling Agent Teams and sharing task inputs among spawned agents.
Before installing, make sure you want Claude Agent Teams enabled and review each workflow’s scope, inputs, and definition of done before spawning teammates. Avoid giving the workflow sensitive source material unless all spawned agents should be allowed to see it.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Enabling Agent Teams may affect future Claude Code sessions until the setting is removed.
The skill requires a manual persistent Claude settings change even though there is no install spec or declared environment requirement. This is purpose-aligned, but it is still a setup dependency users should notice.
Agent Teams must be enabled. Add to `~/.claude/settings.json`: ... `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS`: `1`
Enable the setting only if you intend to use Agent Teams, and remove it later if you no longer want that feature active.
Any sensitive material used as workflow input may be shared across the whole spawned agent team.
The workflow intentionally passes user requirements, source materials, and intermediate artifacts between spawned teammates and the lead.
INPUT: [Paste or reference the artifact from the previous step. For first step: paste user requirements + source materials.] ... When done, message the lead
Do not include confidential inputs unless you are comfortable with all teammate agents seeing them, and keep task prompts scoped to the minimum needed context.
A bad intermediate result could influence later stages of the workflow before the final review catches it.
Verbatim handoffs preserve context but can also propagate mistakes, misleading content, or embedded instructions from one agent output to later agents.
Lead forwards full plan from Planner to Builder (don't summarize ...); Lead relays Critic's feedback verbatim to Builder (don't filter ...)
Keep the lead responsible for preserving the original user scope and treating handoff artifacts as data, especially when source material may contain instructions or untrusted text.