ck:team

Coordinate independent Claude Code sessions for parallel team workflows.

Updated May 10, 2026
One-click install
npx skills add https://github.com/dthuy62/kollet-app --skill ck-team-dthuy62
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:team
Source: https://github.com/dthuy62/kollet-app/tree/main/.opencode/skills/team
Command: npx skills add https://github.com/dthuy62/kollet-app --skill ck-team-dthuy62

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you coordinate multiple Claude Code teammates when a task is too large, parallel, or discussion-heavy for a single session.

Core Features & Use Cases

  • Parallel research, implementation, review, and debugging across independent teammates.
  • Shared task lists, direct messaging, shutdown flow, and plan approval for safer orchestration.
  • Worktree isolation for implementation teams so each developer can work without file conflicts.

Quick Start

Use the team skill to break this repository analysis into parallel workstreams and coordinate the teammates from a single lead session.

Frequently Asked Questions about ck:team

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

FAQPage Schema
How do I run parallel agent teams for code review and debugging?

A lead Claude Code session coordinates independent teammates for parallel code review and debugging. It applies task, messaging, and worktree orchestration to manage independent workstreams from a single lead session.

What is worktree isolation and when do I need it for parallel implementation?

Worktree isolation creates separate working directories for each teammate, preventing file conflicts during parallel implementation. You need it when multiple agents modify the same repository simultaneously without overwriting each other's changes.

Do I need Opus 4.6 teammates to orchestrate parallel Claude Code sessions?

Yes, coordinating parallel agent teams requires Opus 4.6 teammates, Agent Teams support, and CLI terminal execution. These components ensure reliable task, messaging, and worktree orchestration across independent Claude Code sessions.

Can I coordinate research and implementation workstreams from a single lead session?

Yes, a single lead session coordinates parallel research, implementation, code review, and debugging workstreams. It manages shared task lists, direct messaging, shutdown flow, and plan approval to orchestrate independent teammates.

What's the best way to manage task lists and direct messaging across independent Claude Code sessions?

Using a lead session with task and messaging orchestration provides shared task lists, direct teammate communication, and structured shutdown flow. This approach ensures reliable coordination and safer orchestration across independent Claude Code sessions.

Why does parallel agent team orchestration require CLI terminal execution?

CLI terminal execution is required because orchestrating independent Claude Code sessions depends on terminal-level control to manage multiple teammates, apply worktree isolation, and execute task and messaging coordination reliably.