cc-workspace 5.2.4 → 5.2.5
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/CHANGELOG.md +14 -0
- package/README.md +7 -6
- package/global-skills/agents/team-lead.md +2 -2
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,19 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [5.2.5] — 2026-03-11
|
|
4
|
+
|
|
5
|
+
### Fix: team-lead can now spawn teammates
|
|
6
|
+
|
|
7
|
+
- **Added `Agent` to team-lead tools** — the `Agent` tool was missing from the team-lead's
|
|
8
|
+
tool list, preventing it from spawning implementer teammates. The documented workflow
|
|
9
|
+
(`TeamCreate` → `Agent(subagent_type: "implementer", team_name: ...)` → `SendMessage`)
|
|
10
|
+
was broken because `Agent` was not in the allowed tools. Spawn constraints (implementer
|
|
11
|
+
only) remain enforced by team-lead rules, `validate-spawn-prompt.sh` hook, and
|
|
12
|
+
dispatch-feature documentation.
|
|
13
|
+
|
|
14
|
+
**Files changed:**
|
|
15
|
+
- `agents/team-lead.md` — added `Agent` to tools list, bumped `prompt_version` to 5.2.4
|
|
16
|
+
|
|
3
17
|
## [5.2.3] — 2026-03-10
|
|
4
18
|
|
|
5
19
|
### One implementer per commit unit + User review before commit
|
package/README.md
CHANGED
|
@@ -558,15 +558,16 @@ With `--chrome`, the agent:
|
|
|
558
558
|
|
|
559
559
|
---
|
|
560
560
|
|
|
561
|
-
## Changelog v5.2.0 -> v5.2.
|
|
561
|
+
## Changelog v5.2.0 -> v5.2.5
|
|
562
562
|
|
|
563
563
|
| # | Feature | Detail |
|
|
564
564
|
|---|---------|--------|
|
|
565
|
-
| 1 | **
|
|
566
|
-
| 2 | **
|
|
567
|
-
| 3 | **
|
|
568
|
-
| 4 | **
|
|
569
|
-
| 5 | **
|
|
565
|
+
| 1 | **Agent tool for team-lead** | Fixed missing `Agent` tool in team-lead's tool list — the team-lead can now spawn implementer teammates via `Agent(subagent_type: "implementer", team_name: ...)`. |
|
|
566
|
+
| 2 | **One teammate per commit unit** | Shift from one teammate per repo (handling all commits) to one implementer per commit unit. Eliminates the unreliable "signal and wait" pattern — each implementer handles exactly one unit then stops. |
|
|
567
|
+
| 3 | **User reviews before commit** | Implementers write code without committing. After micro-QA, the team lead presents changes to the user for review. The team lead commits only after user approval. |
|
|
568
|
+
| 4 | **PreToolUse hook blocks git add/commit** | Implementer frontmatter now includes a Bash hook that physically blocks `git add` and `git commit`. Even if the model ignores instructions, commits are prevented. |
|
|
569
|
+
| 5 | **Team lead commits** | The team lead (not the implementer) runs `git add` + `git commit` in the worktree after user approval. Commit tracking includes `user_committed` and `files_modified` fields. |
|
|
570
|
+
| 6 | **Sequential with user gate** | Intra-repo commit units are strictly sequential with a user review gate between each. Cross-repo parallelism is preserved. |
|
|
570
571
|
|
|
571
572
|
---
|
|
572
573
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: team-lead
|
|
3
|
-
prompt_version: 5.2.
|
|
3
|
+
prompt_version: 5.2.5
|
|
4
4
|
description: >
|
|
5
5
|
Main orchestrator for multi-service workspaces. Clarifies specs,
|
|
6
6
|
plans in markdown, manages git (branches, worktrees) directly,
|
|
@@ -9,7 +9,7 @@ description: >
|
|
|
9
9
|
Never codes in repos — can write in orchestrator/ and run git commands.
|
|
10
10
|
Triggered via claude --agent team-lead.
|
|
11
11
|
model: opus
|
|
12
|
-
tools: Read, Write, Edit, Bash, Glob, Grep, Task(Explore), TeamCreate, TeamDelete, SendMessage
|
|
12
|
+
tools: Read, Write, Edit, Bash, Glob, Grep, Task(Explore), Agent, TeamCreate, TeamDelete, SendMessage
|
|
13
13
|
memory: project
|
|
14
14
|
maxTurns: 200
|
|
15
15
|
hooks:
|
package/package.json
CHANGED