ck:team

Coordinate multiple AI agent sessions for parallel collaborative workflows.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/quanganh208/cookmate --skill ck-team-quanganh208
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:team
Source: https://github.com/quanganh208/cookmate/tree/main/.opencode/skills/team
Command: npx skills add https://github.com/quanganh208/cookmate --skill ck-team-quanganh208

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinate and manage multiple independent AI teammate sessions to run parallel, inter-communicating workflows so a single lead does not have to perform all research, implementation, review, or debugging tasks sequentially.

Core Features & Use Cases

  • Parallel team orchestration: Spawn multiple teammates (researchers, developers, reviewers, debuggers) that run concurrently and communicate via a shared task list and SendMessage channels.
  • Worktree isolation for implementation: Give each developer an isolated git worktree and branch to avoid file conflicts, then merge branches after completion.
  • Event-driven monitoring & lifecycle: Use TeamCreate, TaskCreate, TaskCompleted hooks, and TeamDelete to manage team lifecycle, monitor progress, synthesize reports, and clean up.
  • Use case: Run a cook workflow with three devs and one tester to implement a feature in parallel, have the tester run the suite, merge worktree branches, and produce a final report.

Quick Start

Run /ck:team cook <plan-or-description> --devs 3 to spawn isolated developer teammates, run implementation and testing in parallel, merge branches, and produce a final report.

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 AI agent workflows for code review and debugging?

You can orchestrate parallel AI agent workflows by spawning multiple independent teammate sessions that run concurrently, communicate via a shared task list, and use SendMessage channels to coordinate code review, debugging, or research tasks.

What is git worktree isolation and how does it prevent file conflicts during parallel development?

Git worktree isolation gives each parallel developer teammate an isolated git worktree and branch to prevent file conflicts during concurrent implementation, allowing branches to be merged together cleanly after task completion.

How do I manage the lifecycle of parallel agent teams from creation to cleanup?

You manage agent team lifecycles using TeamCreate to spawn sessions, TaskCreate and TaskCompleted hooks to monitor progress, and TeamDelete to clean up resources after synthesizing final reports.

Can I use parallel agent teams for concurrent feature implementation and testing?

Yes, you can spawn multiple developer teammates and a tester to implement features concurrently, run the test suite in parallel, merge worktree branches, and produce a final report without sequential bottlenecks.

Do I need a CLI terminal environment to orchestrate parallel agent teams?

Yes, orchestrating parallel agent teams requires a CLI terminal environment along with Agent Teams enabled and Opus 4.6 for all teammates to execute tool calls like TeamCreate, TaskCreate, and SendMessage properly.