/CCteam-creator

name: CCteam-creator
description: >
  Set up a complete agent team with file-based planning for complex multi-agent projects.
  Use when: (1) user asks to start a new complex project with a team/swarm, (2) user says
  "set up team", "create team", "build a team for X", "start project X", (3) user invokes
  /CCteam-creator with a project name, (4) user wants to organize a multi-phase project
  with parallel agent workers and persistent progress tracking. Creates TeamCreate, planning
  files (.plans/project/), per-agent work directories, and spawns configured
  teammates. TRIGGER on: "team", "swarm", "start project", "set up project", "create team
  for", "build team", "organize project", "multi-agent project".
  IMPORTANT: You (team-lead) MUST read all reference files directly — do NOT delegate to subagents.
  NOTE: After initial setup, you can add new teammates at any time — just spawn a new Agent with the team_name and follow the same onboarding pattern. The team is not locked after creation.

Team Project Setup

Set up a multi-agent team for complex projects, using persistent files for planning and progress tracking.

Prerequisites

**Before starting Step 1**, you (team-lead) MUST read all reference files directly into your own context:

Read references/onboarding.md
Read references/templates.md
Read references/roles.md

Do NOT delegate this to a subagent (Explore, general-purpose, etc.). Subagents return summaries, losing critical detail — you need the full templates and onboarding prompts to generate files and spawn agents correctly.

Process

**Step 0 Update Check (auto)**: Background version fetch + one-line notification if newer version exists **Step 0 Detect (auto)**: Check if `.plans/` exists → if yes, offer to resume existing project 1. **Requirements Consultation** — Introduce the team mechanism to the user and gather requirements 2. **Confirm the Plan** — Summarize requirements and let the user confirm the team configuration 3. Create planning files (including per-agent subdirectories) 4. Create the team + spawn agents 5. Confirm setup + guide user to compact context

Step 0 Update Check: Version Self-Check (Auto — Before Anything Else, ~2s)

Before any other step, perform a lightweight version check. **No user consent needed, do not ask any questions.**

1. **Remote version**: WebFetch `https://raw.githubusercontent.com/jessepwj/CCteam-creator/master/.claude-plugin/plugin.json` with prompt: "What is the value of the version field? Respond with just the version string." 2. **Local version**: Use Bash to read local plugin.json (try these paths in order, use the first that exists):

   cat ~/.claude/plugins/cache/ccteam/CCteam-creator/*/.claude-plugin/plugin.json 2>/dev/null || \
   cat ~/.claude/plugins/cache/ccteam/CCteam-creator-cn/*/.claude-plugin/plugin.json 2>/dev/null || \
   cat ~/.claude/skills/CCteam-creator/.claude-plugin/plugin.json 2>/dev/null

Extract the version field from the output. 3. **Compare**:

• **remote ≤ local**, OR **WebFetch failed**, OR **local plugin.json not found** → **completely silent**, proceed to the next step. Do NOT print "version check passed" or any confirmation noise
• **remote > local** → print **one** notification line (just one, then immediately continue, do NOT wait for user reply):

> ℹ️ A newer CCteam-creator version is available (<local> → <remote>). It will auto-apply on next Claude Code startup. Continuing with <local> in this session. For immediate effect: `/plugin marketplace update ccteam` → `/exit` → restart → re-trigger this skill.

**Hard rules**:

• ❌ Do NOT ask the user "continue with old version?" — no confirmation at all
• ❌ Do NOT attempt to Bash-update the plugin cache yourself — that's Claude Code's job, not the skill's
• ❌ Do NOT render the version check as a visible task in TodoWrite/TaskCreate — it should run in the background invisibly
• ❌ If the network fails, do NOT retry — just proceed
• ✅ At most one notification line, then **immediately** proceed to the next step

Step 0 Detect: Detect Existing Project (Auto — Before Anything Else)

Before starting setup, check if `.plans/` directory exists in the current working directory.

**If `.plans/` exists**: 1. Read the project CLAUDE.md (auto-loaded) to get the team roster and project context 2. Scan `.plans/` for project directories — if multiple, list them 3. Tell the user: "I found an existing project [name] with [roster]. Resume this project or start a new one?" 4. **If resume**: a. Check if `.plans/<project>/team-snapshot.md` exists b. **If snapshot exists**: Read the snapshot header metadata. Compare skill source file timestamps against snapshot generation time:

• **Source files unchanged** → use cached onboarding prompts from snapshot to spawn agents directly (skip reading skill reference files)
• **Source files changed** → inform user: "Skill files have been updated since this team was created. Use cached config for fast resume, or re-read skill files to pick up latest protocols?" Let user decide

c. **If no snapshot**: Fall back to reading all skill reference files (onboarding.md, roles.md) to rebuild onboarding prompts, then spawn agents d. After spawning, check TaskList / read progress files to pick up where things left off 5. **If new**: Proceed to Step 1 as normal

**If `.plans/` does not exist**: Skip directly to Step 1.

Step 1: Requirements Consultation (Talk First, Then Act)

**Goal of this step**: Help the user fully understand how the team works, while gathering their actual requirements. Do not rush to create any files or teams.

1.1 Introduce the Team Mechanism

In a natural, conversational tone (do not copy this text verbatim — adapt to context), explain the following points:

**What a team is**:

• You (Claude) act as team-lead, simultaneously directing multiple AI agents working in parallel
• Team-lead is the **main conversation control plane**, not a spaw