ckteamlisted

# Agent Teams - CK-Native Orchestration Engine Coordinate multiple independent Claude Code sessions. Each teammate has own context window, loads project context (CLAUDE.md, skills, agents), communicates via shared task list and messaging. **Requires:** Agent Teams enabled. Set `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` in settings.json env. **Requires:** CLI terminal — `TaskCreate`/`TaskUpdate`/`TaskGet`/`TaskList` and `TeamCreate`/`TeamDelete` are **disabled in VSCode extension** (`isTTY` check). Agent Teams CANNOT run in VSCode. **Model requirement:** All teammates must run Opus 4.6 (Agent Teams constraint). ## Usage ``` /ck:team <template> <context> [flags] ``` **Templates:** `ck:research`, `ck:cook`, `ck:code-review`, `ck:debug` **Flags:** - `--devs N` | `--researchers N` | `--reviewers N` | `--debuggers N` -- team size - `--plan-approval` / `--no-plan-approval` -- plan gate (default: on for cook) - `--delegate` -- lead only coordinates, never touches code - `--worktree` -- use git worktrees for implementation isolation (default: on for cook) ## Execution Protocol **Pre-flight (MANDATORY -- merged into step 2 of every template):** 1. Step 2 of every template calls `TeamCreate(team_name: "...", ...)`. Do NOT check whether the tool exists first -- just call it. 2. If the call SUCCEEDS: continue with the template. 3. If the call returns an ERROR or is unrecognized: **STOP. Tell user:** "Agent Teams requires `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` in settings.json. Tea