team

Coordinate multiple Claude Code teammates for parallel multi-session collaboration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Orchestrate multiple Claude Code sessions as a single coordinated team, enabling independent teammates to work in parallel with their own contexts, while sharing a common task list and messaging channels.

Core Features & Use Cases

  • Create and manage an Agent Team (lead + teammates) to tackle complex tasks in parallel (research, implementation, review, debug) with isolated file ownership and clear handoffs.
  • Spawn, assign, monitor, and synthesize results from multiple teammates using task dependencies and event-driven hooks (TaskCompleted, TeammateIdle) for reactive coordination.
  • Support memory and cross-session continuity, plus a structured clean up process (shutdown and TeamDelete) after work completes.

Quick Start

Spawn an agent team for a feature, then let teammates report back via tasks and synthesize a final summary.

Frequently Asked Questions about team

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

FAQPage Schema
How do I coordinate parallel Claude Code sessions for multi-session collaboration?

Parallel Claude Code sessions are coordinated by creating an agent team with a lead and multiple teammates. Teammates work independently with isolated contexts while sharing a common task list and messaging channels to achieve multi-session collaboration.

How does event-driven coordination work for managing parallel agent tasks?

Event-driven coordination uses TaskCompleted and TeammateIdle hooks to monitor teammate progress. When a teammate finishes a task or becomes idle, these hooks trigger reactive coordination so the lead can assign new tasks or synthesize results automatically.

Can I use multiple Claude Code teammates for parallel research and implementation workflows?

Yes, multiple Claude Code teammates can be spawned for parallel research, implementation, review, and debugging workflows. Each teammate gets isolated file ownership and clear handoffs to manage independent work without conflicts.

What is the best way to manage task dependencies across multiple agent teammates?

Task dependencies across agent teammates are managed through a shared task list. The lead assigns tasks, monitors progress via event hooks, and synthesizes final results once teammates report back, ensuring structured handoffs before executing a clean shutdown.

How do I shut down an agent team after parallel work is completed?

Agent teams are shut down by executing a clean cleanup process after work completes. This involves synthesizing the final summary, triggering the shutdown command, and using TeamDelete to safely remove the team and its cross-session memory.

When should I use multi-session agent teams instead of a single Claude Code session?

Multi-session agent teams are ideal for complex tasks requiring parallel execution, such as simultaneous research and implementation. If a task needs independent contexts with isolated file ownership and clear handoffs, team coordination outperforms a single session.