ck:team

Parallel agent teams are coordinated using a single lead Claude Code session to orchestrate multiple teammates through team creation, task assignment, and inter-teammate messaging. This enables simultaneous research, implementation, review, and debugging workflows across independent sessions.

Worktree isolation provides separate branching environments for code changes made by parallel teammates. It ensures independent development sessions do not conflict, allowing a clean merge of all code changes after the parallel tasks are completed.

Event-driven monitoring tracks team progress using TaskCompleted and TeammateIdle events. This allows the lead session to dynamically monitor teammate status, reassign pending tasks to idle agents, and clean up resources upon completion.

Multi-module codebase development is managed by spawning cross-session agent teams with a lead coordinating independent teammates. Templates for end-to-end collaboration handle parallel workflows, synthesizing results from long-running research and complex debugging scenarios.

Templates are available to quickly initiate end-to-end collaboration for specific workflows. Commands like /ck:team cook, /ck:team review, and /ck:team debug provide structured scopes for parallel implementation, code review, and debugging tasks.

Team orchestration provides centralized coordination that independent sessions lack, enabling inter-teammate messaging, event-driven task tracking, and automated worktree isolation. This structured approach ensures clean merges and synthesized results for complex parallel tasks.