ck:team

Agent Teams - CK-Native Orchestration Engine

Coordinate multiple independent Codex sessions. Each teammate has own context window, loads project context (AGENTS.md, skills, agents), communicates via shared task list and messaging.

Requires: Agent Teams enabled. Set CODEX_EXPERIMENTAL_AGENT_TEAMS=1 in settings.json env if using Codex < 2.1.33. May be GA in 2.1.33+.

Usage

$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

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 CODEX_EXPERIMENTAL_AGENT_TEAMS=1 in settings.json. Team mode is not available."
4. Do NOT fall back to subagents. $team MUST use Agent Teams or abort.
5. All teammate spawns MUST include team_name parameter — never spawn Task without it.

When activated, IMMEDIATELY execute the matching template sequence below. Do NOT ask for confirmation. Do NOT explain what you're about to do. Execute the tool calls in order. Report progress after each major step.

---

CK Context Block

Every teammate spawn prompt MUST include this context at the end:

CK Context:
- Work dir: {CK_PROJECT_ROOT or CWD}
- Reports: {CK_REPORTS_PATH or "plans/reports/"}
- Plans: {CK_PLANS_PATH or "plans/"}
- Branch: {CK_GIT_BRANCH or current branch}
- Naming: {CK_NAME_PATTERN or "YYMMDD-HHMM"}
- Active plan: {CK_ACTIVE_PLAN or "none"}
- Commits: conventional (feat:, fix:, docs:, refactor:, test:, chore:)
- Refer to teammates by NAME, not agent ID