Support for Claude Code Agent Teams (TeammateTool, SendMessage, TaskList)

[evrenverse]

Is your feature request related to a problem? Please describe.

Claude Code 2.1.32+ introduced experimental Agent Teams — a feature that allows coordinating multiple Claude Code instances as a team with a lead, teammates, shared task lists, and inter-agent messaging. See the official documentation.

Superpowers currently has skills for subagent-driven development (subagent-driven-development, dispatching-parallel-agents) but no awareness of or support for the newer Agent Teams primitives. When using superpowers with agent teams, several issues arise:

1. Skills don't recognize team context. Skills like executing-plans and subagent-driven-development only know about the Task tool (subagents), not Teammate, SendMessage, or the team-aware TaskCreate/TaskUpdate/TaskList tools.
2. No skill for orchestrating agent teams. There's no skill that guides the team lead on how to break down work, spawn teammates, assign tasks, handle plan approvals, and coordinate shutdown — the way dispatching-parallel-agents does for subagents.
3. Existing parallel-work skills may conflict. dispatching-parallel-agents spawns subagents via the Task tool. In a team context, the lead should use Teammate + SendMessage instead. Using both simultaneously creates confusion.

Describe the solution you'd like

1. A new agent-teams skill (or extension of dispatching-parallel-agents) that:

   • Detects whether Agent Teams tools (Teammate, SendMessage, TaskList) are available
   • Guides the lead through team creation, task breakdown, teammate spawning, and task assignment
   • Covers plan approval workflows (reviewing teammate plans, approving/rejecting)
   • Handles graceful shutdown and cleanup
   • Includes best practices from the docs: sizing tasks appropriately, avoiding file conflicts, giving teammates enough context, using delegate mode

2. Team-aware adaptations for existing skills:

   • executing-plans: When running inside a team, delegate plan steps to teammates instead of subagents
   • verification-before-completion: Coordinate verification across teammates before claiming team-wide completion
   • requesting-code-review / receiving-code-review: Support teammate-to-teammate code review via SendMessage

3. Teammate-side skill awareness:

   • Skills invoked by a teammate should know they're running in a team context (can message lead/peers, can read shared task list)
   • A teammate receiving a shutdown request should handle it gracefully (approve/reject via shutdown_response)

Describe alternatives you've considered

• Do nothing: Users manually adapt subagent-focused skills for team use. Works but loses the structured guidance that makes superpowers effective.
• Just update dispatching-parallel-agents: Add a conditional branch for teams vs. subagents. Simpler but may make the skill too complex.
• Environment detection only: Add a utility that detects team context and adjusts tool selection, without a dedicated skill. Lightweight but doesn't provide orchestration guidance.

Additional context

• Agent Teams require CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 in settings
• Key tools: Teammate (spawnTeam, cleanup), SendMessage (message, broadcast, shutdown_request/response, plan_approval_response), TaskCreate, TaskUpdate, TaskList, TaskGet
• Teams are stored at ~/.claude/teams/{team-name}/config.json and ~/.claude/tasks/{team-name}/
• The feature is experimental with known limitations (no session resumption, no nested teams, one team per session)
• Reference: https://code.claude.com/docs/en/agent-teams

[bok-]

Can't say these are full or complete, but they've been working great for me so far so thought I'd share.

Mostly these are just the result of asking Claude to adapt writing-plans and subagent-driven-development into writing-plans-for-teams and agent-team-driven-development, respectively. The former contains a fitness check to see whether the plan can be run in parallel by a team, otherwise it falls back to the original skills.

They work pretty well - the lead runs the team and manages dispatching of spec reviewer + code reviewer subagents in parallel as tasks complete. There are definitely potential opportunities to split that out into dedicated team members rather than subagents, as well as better collaboration between team members, but its working for now.

agent-team-skills.zip

[pySilver]

@bok- you simply put these skills into your .claude or your fork of superpowers?

[ChuckFul]

@bok- I am having some success with these skills. Plan creation, team member dispatch, as well as spec compliance and code review all working seamlessly so far. Thank you for sharing.

[Divkix]

This would be a killer feature if superpowers is able to integrate with Claude Agents Team

[cristianj26]

+1 I currently have a fork that uses a .md file for team-parallel-agents and team-driven-development but would prefer it in the proper repo

[klatimer]

+1 this is fantastic - looking forward to it being available on main!