ccg-workflow 1.7.59 → 1.7.60

package/README.md

@@ -48,6 +48,10 @@ npx ccg-workflow
 | `/ccg:spec-plan` | 约束 → 零决策计划 |
 | `/ccg:spec-impl` | 按计划执行 + 归档 |
 | `/ccg:spec-review` | 双模型交叉审查 |
+| `/ccg:team-research` | Agent Teams 需求 → 约束集 |
+| `/ccg:team-plan` | Agent Teams 约束 → 并行计划 |
+| `/ccg:team-exec` | Agent Teams 并行实施 |
+| `/ccg:team-review` | Agent Teams 双模型审查 |
 
 ### OPSX 规范驱动（v1.7.52+）
 
@@ -72,6 +76,28 @@ npx ccg-workflow
 
 **说明**：`/ccg:spec-*` 命令是 CCG 对 OPSX 的封装，内部调用 `/opsx:*` 命令。每阶段之间可 `/clear`，状态存在 `openspec/` 目录，不怕上下文爆。
 
+### Agent Teams 并行实施（v1.7.60+）
+
+利用 Claude Code Agent Teams 实验特性，spawn 多个 Builder teammates 并行写代码：
+
+```bash
+# 1. 需求研究 → 约束集（复杂项目推荐，简单项目可跳过）
+/ccg:team-research 实现实时协作看板 API
+
+# 2. /clear 后规划 → 零决策并行计划
+/ccg:team-plan kanban-api
+
+# 3. /clear 后并行实施 → Builder teammates 并行写代码
+/ccg:team-exec
+
+# 4. /clear 后审查 → 双模型交叉审查
+/ccg:team-review
+```
+
+**前置条件**：需手动启用 Agent Teams（`settings.json` 中设置 `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`）
+
+**vs 传统工作流**：Team 系列每步 `/clear` 隔离上下文，通过文件传递状态。Builder 并行实施，适合可拆分为 3+ 独立模块的任务。
+
 ### 规划与执行分离
 
 v1.7.39 新增 `/ccg:plan` 和 `/ccg:execute` 命令，将规划与执行解耦：
@@ -211,4 +237,4 @@ MIT
 
 ---
 
-v1.7.57 | [Issues](https://github.com/fengshao1227/ccg-workflow/issues)
+v1.7.60 | [Issues](https://github.com/fengshao1227/ccg-workflow/issues)

package/dist/cli.mjs

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 import cac from 'cac';
 import ansis from 'ansis';
-import { z as diagnoseMcpConfig, A as isWindows, B as readClaudeCodeConfig, C as fixWindowsMcpConfig, D as writeClaudeCodeConfig, r as readCcgConfig, b as initI18n, s as showMainMenu, i as init, E as configMcp, F as version, a as i18n } from './shared/ccg-workflow.BDEqkVoT.mjs';
+import { z as diagnoseMcpConfig, A as isWindows, B as readClaudeCodeConfig, C as fixWindowsMcpConfig, D as writeClaudeCodeConfig, r as readCcgConfig, b as initI18n, s as showMainMenu, i as init, E as configMcp, F as version, a as i18n } from './shared/ccg-workflow.flWlQcrI.mjs';
 import 'inquirer';
 import 'node:child_process';
 import 'node:util';

package/dist/index.mjs

@@ -1,4 +1,4 @@
-export { c as changeLanguage, x as checkForUpdates, y as compareVersions, d as createDefaultConfig, e as createDefaultRouting, g as getCcgDir, f as getConfigPath, t as getCurrentVersion, v as getLatestVersion, j as getWorkflowById, h as getWorkflowConfigs, a as i18n, i as init, b as initI18n, l as installAceTool, m as installAceToolRs, k as installWorkflows, p as migrateToV1_4_0, q as needsMigration, r as readCcgConfig, s as showMainMenu, o as uninstallAceTool, n as uninstallWorkflows, u as update, w as writeCcgConfig } from './shared/ccg-workflow.BDEqkVoT.mjs';
+export { c as changeLanguage, x as checkForUpdates, y as compareVersions, d as createDefaultConfig, e as createDefaultRouting, g as getCcgDir, f as getConfigPath, t as getCurrentVersion, v as getLatestVersion, j as getWorkflowById, h as getWorkflowConfigs, a as i18n, i as init, b as initI18n, l as installAceTool, m as installAceToolRs, k as installWorkflows, p as migrateToV1_4_0, q as needsMigration, r as readCcgConfig, s as showMainMenu, o as uninstallAceTool, n as uninstallWorkflows, u as update, w as writeCcgConfig } from './shared/ccg-workflow.flWlQcrI.mjs';
 import 'ansis';
 import 'inquirer';
 import 'node:child_process';

package/dist/shared/{ccg-workflow.BDEqkVoT.mjs → ccg-workflow.flWlQcrI.mjs}

@@ -10,7 +10,7 @@ import i18next from 'i18next';
 import ora from 'ora';
 import { parse, stringify } from 'smol-toml';
 
-const version = "1.7.59";
+const version = "1.7.60";
 
 function isWindows() {
   return process.platform === "win32";
@@ -411,6 +411,50 @@ const WORKFLOW_CONFIGS = [
     order: 34,
     description: "\u53CC\u6A21\u578B\u4EA4\u53C9\u5BA1\u67E5 \u2192 Critical \u5FC5\u987B\u4FEE\u590D \u2192 \u5141\u8BB8\u5F52\u6863",
     descriptionEn: "Multi-model compliance review before archiving"
+  },
+  {
+    id: "team-research",
+    name: "Agent Teams \u9700\u6C42\u7814\u7A76",
+    nameEn: "Agent Teams Research",
+    category: "development",
+    commands: ["team-research"],
+    defaultSelected: true,
+    order: 1.8,
+    description: "\u5E76\u884C\u63A2\u7D22\u4EE3\u7801\u5E93\uFF0C\u4EA7\u51FA\u7EA6\u675F\u96C6 + \u53EF\u9A8C\u8BC1\u6210\u529F\u5224\u636E",
+    descriptionEn: "Parallel codebase exploration, produces constraint sets + success criteria"
+  },
+  {
+    id: "team-plan",
+    name: "Agent Teams \u89C4\u5212",
+    nameEn: "Agent Teams Planning",
+    category: "development",
+    commands: ["team-plan"],
+    defaultSelected: true,
+    order: 2,
+    description: "Lead \u8C03\u7528 Codex/Gemini \u5E76\u884C\u5206\u6790\uFF0C\u4EA7\u51FA\u96F6\u51B3\u7B56\u5E76\u884C\u5B9E\u65BD\u8BA1\u5212",
+    descriptionEn: "Lead orchestrates Codex/Gemini analysis, produces zero-decision parallel plan"
+  },
+  {
+    id: "team-exec",
+    name: "Agent Teams \u5E76\u884C\u5B9E\u65BD",
+    nameEn: "Agent Teams Parallel Execution",
+    category: "development",
+    commands: ["team-exec"],
+    defaultSelected: true,
+    order: 2.5,
+    description: "\u8BFB\u53D6\u8BA1\u5212\u6587\u4EF6\uFF0Cspawn Builder teammates \u5E76\u884C\u5199\u4EE3\u7801\uFF0C\u9700\u542F\u7528 Agent Teams",
+    descriptionEn: "Read plan file, spawn Builder teammates for parallel implementation"
+  },
+  {
+    id: "team-review",
+    name: "Agent Teams \u5BA1\u67E5",
+    nameEn: "Agent Teams Review",
+    category: "development",
+    commands: ["team-review"],
+    defaultSelected: true,
+    order: 3,
+    description: "\u53CC\u6A21\u578B\u4EA4\u53C9\u5BA1\u67E5\u5E76\u884C\u5B9E\u65BD\u4EA7\u51FA\uFF0C\u5206\u7EA7\u5904\u7406 Critical/Warning/Info",
+    descriptionEn: "Dual-model cross-review with severity classification"
   }
 ];
 function getWorkflowConfigs() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ccg-workflow",
-  "version": "1.7.59",
+  "version": "1.7.60",
   "description": "Claude-Codex-Gemini 多模型协作系统 - 智能路由多模型开发工作流",
   "type": "module",
   "packageManager": "pnpm@10.17.1",

package/templates/commands/debug.md

@@ -24,31 +24,35 @@ description: '多模型调试：Codex 后端诊断 + Gemini 前端诊断，交
 ## 多模型调用规范
 
 **工作目录**：
-- `{{WORKDIR}}`：替换为目标工作目录的**绝对路径**
 - 如果用户通过 `/add-dir` 添加了多个工作区，先用 Glob/Grep 确定任务相关的工作区
 - 如果无法确定，用 `AskUserQuestion` 询问用户选择目标工作区
-- 默认使用当前工作目录
+- 默认使用当前工作目录（通过 `pwd` 命令获取）
 
-**调用语法**（并行用 `run_in_background: true`）：
+**调用示例**：
 
-```
-Bash({
-  command: "~/.claude/bin/codeagent-wrapper {{LITE_MODE_FLAG}}--backend <codex|gemini> {{GEMINI_MODEL_FLAG}}- \"{{WORKDIR}}\" <<'EOF'
-ROLE_FILE: <角色提示词路径>
+**Codex 后端诊断**：
+```bash
+~/.claude/bin/codeagent-wrapper --backend codex - "$(pwd)" <<'EOF'
+ROLE_FILE: ~/.claude/.ccg/prompts/codex/debugger.md
 <TASK>
-需求：<增强后的需求（如未增强则用 $ARGUMENTS）>
-上下文：<错误日志、堆栈信息、复现步骤等>
+需求：<增强后的需求>
+上下文：<错误日志、堆栈信息、复现步骤>
 </TASK>
 OUTPUT: 诊断假设（按可能性排序）
-EOF",
-  run_in_background: true,
-  timeout: 3600000,
-  description: "简短描述"
-})
+EOF
 ```
 
-**模型参数说明**：
-- `{{GEMINI_MODEL_FLAG}}`：当使用 `--backend gemini` 时，替换为 `--gemini-model gemini-3-pro-preview `（注意末尾空格）；使用 codex 时替换为空字符串
+**Gemini 前端诊断**：
+```bash
+~/.claude/bin/codeagent-wrapper --backend gemini --gemini-model gemini-3-pro-preview - "$(pwd)" <<'EOF'
+ROLE_FILE: ~/.claude/.ccg/prompts/gemini/debugger.md
+<TASK>
+需求：<增强后的需求>
+上下文：<错误日志、堆栈信息、复现步骤>
+</TASK>
+OUTPUT: 诊断假设（按可能性排序）
+EOF
+```
 
 **角色提示词**：
 
@@ -57,18 +61,15 @@ EOF",
 | Codex | `~/.claude/.ccg/prompts/codex/debugger.md` |
 | Gemini | `~/.claude/.ccg/prompts/gemini/debugger.md` |
 
-**并行调用**：使用 `run_in_background: true` 启动，用 `TaskOutput` 等待结果。**必须等所有模型返回后才能进入下一阶段**。
-
-**等待后台任务**（使用最大超时 600000ms = 10 分钟）：
-
-```
-TaskOutput({ task_id: "<task_id>", block: true, timeout: 600000 })
-```
+**并行调用**：
+1. 使用 `Bash` 工具，设置 `run_in_background: true` 和 `timeout: 600000`（10 分钟）
+2. 同时发起两个后台任务（Codex + Gemini）
+3. 使用 `TaskOutput` 等待结果：`TaskOutput({ task_id: "<task_id>", block: true, timeout: 600000 })`
 
 **重要**：
-- 必须指定 `timeout: 600000`，否则默认只有 30 秒会导致提前超时。
-如果 10 分钟后仍未完成，继续用 `TaskOutput` 轮询，**绝对不要 Kill 进程**。
-- 若因等待时间过长跳过了等待 TaskOutput 结果，则**必须调用 `AskUserQuestion` 工具询问用户选择继续等待还是 Kill Task。禁止直接 Kill Task。**
+- 必须指定 `timeout: 600000`，否则默认 30 秒会超时
+- 如果 10 分钟后仍未完成，继续用 `TaskOutput` 轮询，**绝对不要 Kill 进程**
+- 若等待时间过长，**必须用 `AskUserQuestion` 询问用户是否继续等待，禁止直接 Kill**
 
 ---