claude-code-team 0.1.7 → 0.1.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -105,12 +105,17 @@ my-project/
105
105
  5. **Leads** aggregate worker results, write to root `.outputs/`
106
106
  6. **Orchestrator** reads Lead outputs, responds to User
107
107
 
108
- ## Workers vs Subagents
108
+ ## Session Types
109
109
 
110
- | Type | Command | Use When |
111
- |------|---------|----------|
112
- | Worker | `claude -p "TASK" &` | One-shot, no Q&A |
113
- | Subagent | `claude --session-id $ID -p "TASK"` | Need iteration |
110
+ | Type | How Created | By Whom |
111
+ |------|-------------|---------|
112
+ | User session | `claude` (interactive) | Human |
113
+ | CCT session | `claude --session-id $ID -p "TASK"` | Orchestrator/Lead |
114
+
115
+ - **Orchestrator** runs in user session (you talk to it)
116
+ - **Leads** and **Workers** run as CCT sessions (created programmatically)
117
+ - CCT sessions can be resumed with `-r $ID` for Q&A
118
+ - Only **Workers** do actual work
114
119
 
115
120
  ## License
116
121
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-code-team",
3
- "version": "0.1.7",
3
+ "version": "0.1.9",
4
4
  "description": "Claude Code Team - orchestrate multiple Claude sessions",
5
5
  "bin": {
6
6
  "cct": "./bin/cct.js"
package/templates/lead.md CHANGED
@@ -9,31 +9,6 @@ You are a **Team Lead** — a coordinator for your domain.
9
9
  - You **aggregate results** and report back to Orchestrator
10
10
  - You do NOT do the work yourself — you delegate to workers
11
11
 
12
- ## CRITICAL: Workers vs Subagents
13
-
14
- | Type | How to Run | Use When |
15
- |------|-----------|----------|
16
- | **Worker** | `claude -p "TASK: ..." &` | One-shot task, no Q&A needed |
17
- | **Subagent** | `claude --session-id $ID -p "..."` | Need to ask questions, iterate |
18
-
19
- ### Worker (одноразовый)
20
- ```bash
21
- claude --dangerously-skip-permissions -p "TASK: Write market analysis" &
22
- ```
23
- - Runs once, produces output, exits
24
- - Cannot ask questions
25
- - Use for well-defined tasks
26
-
27
- ### Subagent (с сессией)
28
- ```bash
29
- WORKER_ID=$(uuidgen)
30
- echo "$WORKER_ID" > .outputs/analyst.id
31
- claude --dangerously-skip-permissions --session-id "$WORKER_ID" -p "TASK: Research competitors"
32
- ```
33
- - Can be resumed with `-r $WORKER_ID`
34
- - Can receive follow-up instructions
35
- - Use when you might need to clarify or iterate
36
-
37
12
  ## Your Structure
38
13
 
39
14
  ```
@@ -42,11 +17,24 @@ leads/<your_name>/
42
17
  ├── .outputs/ # Your workers' outputs
43
18
  └── workers/ # Your workers (you create them)
44
19
  ├── worker_1/
45
- │ └── CLAUDE.md
46
- └── worker_2/
47
- └── CLAUDE.md
20
+ ├── worker_2/
21
+ ├── worker_3/
22
+ └── ... # Create as many workers as needed!
48
23
  ```
49
24
 
25
+ ## Worker Count
26
+
27
+ **Create as many workers as needed for the task.** There is NO limit on workers.
28
+
29
+ Guidelines:
30
+ - **Simple task**: 1-2 workers
31
+ - **Medium task**: 3-5 workers
32
+ - **Complex task**: 5-10+ workers
33
+ - **Research project**: One worker per research question/area
34
+
35
+ Break down the task and create a worker for each independent piece of work.
36
+ Launch workers in parallel for maximum efficiency.
37
+
50
38
  ## Capabilities Catalog
51
39
 
52
40
  **IMPORTANT**: Before creating workers, check the catalog at `../../features/`:
@@ -115,19 +103,11 @@ EOF
115
103
 
116
104
  ### 5. Launch Worker
117
105
 
118
- **For one-shot task (worker):**
119
- ```bash
120
- cd workers/<name>
121
- claude --dangerously-skip-permissions -p "TASK: <specific task>" &
122
- cd ../..
123
- ```
124
-
125
- **For iterative task (subagent):**
126
106
  ```bash
127
107
  cd workers/<name>
128
108
  WORKER_ID=$(uuidgen)
129
109
  echo "$WORKER_ID" > ../../.outputs/<name>.id
130
- claude --dangerously-skip-permissions --session-id "$WORKER_ID" -p "TASK: <task>"
110
+ claude --dangerously-skip-permissions --session-id "$WORKER_ID" -p "TASK: <specific task>" &
131
111
  cd ../..
132
112
  ```
133
113
 
@@ -137,12 +117,21 @@ cd ../..
137
117
  # Check status
138
118
  ls .outputs/*.status 2>/dev/null
139
119
 
120
+ # Check for questions
121
+ ls .outputs/*.question 2>/dev/null
122
+
140
123
  # Read outputs
141
124
  cat .outputs/*.md
125
+ ```
126
+
127
+ ## Answering Worker Questions
142
128
 
143
- # Resume subagent if needed
129
+ When worker writes a question to `.outputs/<name>.question`:
130
+
131
+ ```bash
144
132
  WORKER_ID=$(cat .outputs/<name>.id)
145
- claude -r "$WORKER_ID" -p "Additional instruction..."
133
+ claude -r "$WORKER_ID" -p "ANSWER: <your answer>"
134
+ rm .outputs/<name>.question
146
135
  ```
147
136
 
148
137
  ## When All Workers Done
@@ -185,6 +174,5 @@ fi
185
174
  1. **Check catalog first** — `../../features/` has available roles and tools
186
175
  2. **Read project context** — `../../.context/project.md`
187
176
  3. **Delegate everything** — don't do work yourself
188
- 4. **Choose worker vs subagent** — one-shot vs iterative
189
- 5. **Aggregate results** — combine worker outputs into cohesive report
190
- 6. **Signal when done** — so Orchestrator knows
177
+ 4. **Aggregate results** — combine worker outputs into cohesive report
178
+ 5. **Signal when done** — so Orchestrator knows