agent-team

Coordinate parallel Claude Code agents with shared tasks and messaging.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/cosmicdreams/claude-plugins --skill agent-team-cosmicdreams
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-team
Source: https://github.com/cosmicdreams/claude-plugins/tree/main/admin/skills/agent-team
Command: npx skills add https://github.com/cosmicdreams/claude-plugins --skill agent-team-cosmicdreams

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of coordinating multiple Claude Code agents so they can share communication context and work from a single, consistent task list instead of acting like isolated workers.

Core Features & Use Cases

  • Shared team channel + task list: Uses TeamCreate to establish a common workspace at ~/.claude/tasks/{team-name}/ for coordinated execution.
  • Task-driven parallel collaboration: Creates one shared task per work unit (TaskCreate) and advances ownership/status as agents progress (TaskUpdate).
  • Real-time coordination via messaging: Spawns agents into the same team (Agent with team_name and name) and coordinates progress and handoffs using SendMessage (including shutdown requests and cleanup via TeamDelete).

Use case examples: run parallel research and synthesis, coordinate cross-functional implementation work, or manage multi-agent workflows that require shared state outside a full sprint:run context.

Quick Start

Instruct the AI to set up an agent team and coordinate parallel agents for your multi-step project workflow using shared tasks and SendMessage.

Frequently Asked Questions about agent-team

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate multiple parallel agents with shared state in Claude Code?

Parallel agent coordination with shared state requires TeamCreate to set up a common workspace, TaskCreate and TaskUpdate for shared task list management, and SendMessage for real-time messaging and handoffs between agents.

What is the best way to manage task ownership across multiple agents outside a sprint workflow?

Cross-agent task ownership outside a sprint:run workflow is managed through a shared team task list where agents claim explicit ownership and advance status via TaskUpdate, coordinated through a shared messaging channel.

Can I use SendMessage to request agent shutdown and cleanup after parallel tasks are done?

Yes, SendMessage can be used to send coordination messages including shutdown requests to agents, after which TeamDelete should be called to clean up the shared workspace and remove the team task list once all parallel work is complete.

Does agent-team require any specific environment setup before spawning parallel agents?

Agent-team requires no external dependencies, but you must call TeamCreate first to establish the shared workspace, and then spawn agents using Agent calls that include the exact team_name and a unique name for each agent.

When should I not use parallel agent coordination with a shared team task list?

Parallel agent coordination with a shared team task list should be avoided if your workflow already operates within a full sprint:run context, as this approach is designed specifically for cross-agent coordination outside of that workflow.

Why do my spawned agents act like isolated workers instead of sharing a task list?

Spawned agents act like isolated workers if they are not spawned into the same team context; you must include the exact team_name and a unique name in each Agent call after TeamCreate to ensure they share communication context and the task list.