mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-05 16:13:08 +08:00
Refactor team collaboration skills and update documentation
- Renamed `team-lifecycle-v5` to `team-lifecycle` across various documentation files for consistency. - Updated references in code examples and usage sections to reflect the new skill name. - Added a new command file for the `monitor` functionality in the `team-iterdev` skill, detailing the coordinator's monitoring events and task management. - Introduced new components for dynamic pipeline visualization and session coordinates display in the frontend. - Implemented utility functions for pipeline stage detection and status derivation based on message history. - Enhanced the team role panel to map members to their respective pipeline roles with status indicators. - Updated Chinese documentation to reflect the changes in skill names and descriptions.
This commit is contained in:
@@ -50,7 +50,7 @@
|
||||
| **Workflow** | workflow-test-fix | session → context → analysis → gen → cycle | 测试生成与修复 |
|
||||
| **Workflow** | workflow-multi-cli-plan | ACE context → CLI discussion → plan → execute | 多视角规划 |
|
||||
| **Workflow** | workflow-skill-designer | - | 创建新技能 |
|
||||
| **Team** | team-lifecycle-v5 | spec pipeline → impl pipeline | 完整生命周期 |
|
||||
| **Team** | team-lifecycle | spec pipeline → impl pipeline | 完整生命周期 |
|
||||
| **Team** | team-planex | planner wave → executor wave | Issue 批量执行 |
|
||||
| **Team** | team-arch-opt | architecture analysis → optimization | 架构优化 |
|
||||
| **Utility** | brainstorm | framework → parallel analysis → synthesis | 多视角创意 |
|
||||
@@ -577,10 +577,10 @@
|
||||
|
||||
| 技能 | 描述 |
|
||||
|-------|-------------|
|
||||
| team-lifecycle-v5 | 带角色规格驱动工作代理的完整团队生命周期 |
|
||||
| team-lifecycle | 带角色规格驱动工作代理的完整团队生命周期 |
|
||||
| team-planex | 规划器 + 执行器波流水线 (用于大批量 Issue 或路线图输出) |
|
||||
| team-coordinate-v2 | 团队协调和编排 |
|
||||
| team-executor-v2 | 带工作代理的任务执行 |
|
||||
| team-coordinate | 团队协调和编排 |
|
||||
| team-executor | 带工作代理的任务执行 |
|
||||
| team-arch-opt | 架构优化技能 |
|
||||
|
||||
### 团队领域技能
|
||||
|
||||
@@ -19,8 +19,8 @@
|
||||
|
||||
| Skill | 功能 | 适用场景 |
|
||||
| --- | --- | --- |
|
||||
| `team-coordinate-v2` | 通用团队协调器(动态角色生成) | 任意复杂任务 |
|
||||
| `team-lifecycle-v5` | 全生命周期团队(规范→实现→测试) | 完整功能开发 |
|
||||
| `team-coordinate` | 通用团队协调器(动态角色生成) | 任意复杂任务 |
|
||||
| `team-lifecycle` | 全生命周期团队(规范→实现→测试) | 完整功能开发 |
|
||||
| `team-planex` | 规划-执行流水线 | Issue 批处理 |
|
||||
| `team-review` | 代码审查团队 | 代码审查、漏洞扫描 |
|
||||
| `team-testing` | 测试团队 | 测试覆盖、用例生成 |
|
||||
@@ -35,7 +35,7 @@
|
||||
| `team-roadmap-dev` | 路线图开发团队 | 分阶段开发、里程碑 |
|
||||
| `team-tech-debt` | 技术债务团队 | 债务清理、代码治理 |
|
||||
| `team-ultra-analyze` | 深度分析团队 | 复杂问题分析、协作探索 |
|
||||
| `team-executor-v2` | 轻量执行器 | 会话恢复、纯执行 |
|
||||
| `team-executor` | 轻量执行器 | 会话恢复、纯执行 |
|
||||
|
||||
---
|
||||
|
||||
@@ -77,7 +77,7 @@
|
||||
|
||||
## Skills 详解
|
||||
|
||||
### team-coordinate-v2
|
||||
### team-coordinate
|
||||
|
||||
**一句话定位**: 通用团队协调器 — 根据任务分析动态生成角色并编排执行
|
||||
|
||||
@@ -106,7 +106,7 @@ team-coordinate --role=coordinator <task>
|
||||
|
||||
---
|
||||
|
||||
### team-lifecycle-v5
|
||||
### team-lifecycle
|
||||
|
||||
**一句话定位**: 全生命周期团队 — 从规范到实现到测试到审查的完整流水线
|
||||
|
||||
@@ -456,7 +456,7 @@ team-analyze <topic>
|
||||
|
||||
---
|
||||
|
||||
### team-executor-v2
|
||||
### team-executor
|
||||
|
||||
**一句话定位**: 轻量执行器 — 恢复会话、纯执行模式
|
||||
|
||||
@@ -487,8 +487,8 @@ team-executor --session=<path>
|
||||
## 最佳实践
|
||||
|
||||
1. **选择合适的团队类型**:
|
||||
- 通用任务 → `team-coordinate-v2`
|
||||
- 完整功能开发 → `team-lifecycle-v5`
|
||||
- 通用任务 → `team-coordinate`
|
||||
- 完整功能开发 → `team-lifecycle`
|
||||
- Issue 批处理 → `team-planex`
|
||||
- 代码审查 → `team-review`
|
||||
- 测试覆盖 → `team-testing`
|
||||
|
||||
@@ -50,7 +50,7 @@ Claude Code Workflow 支持两种团队架构模型:
|
||||
- 所有工作者角色都是运行时动态生成
|
||||
- 支持任意任务类型的动态团队
|
||||
|
||||
2. **team-lifecycle-v5** (全生命周期团队)
|
||||
2. **team-lifecycle** (全生命周期团队)
|
||||
- 基于 team-worker agent 架构
|
||||
- 所有工作者共享同一代理定义
|
||||
- 角色特定的 Phase 2-4 从 markdown 规范加载
|
||||
|
||||
@@ -41,9 +41,9 @@
|
||||
|------|--------|------|------|
|
||||
| **team-lifecycle** | `team lifecycle` | 可变 | 完整 spec/impl/test 生命周期团队(v5,team-worker 架构) |
|
||||
| **team-coordinate** | `team coordinate` | 可变 | 通用团队协调(legacy) |
|
||||
| **team-coordinate-v2** | - | 可变 | team-worker 架构协调 |
|
||||
| **team-coordinate** | - | 可变 | team-worker 架构协调 |
|
||||
| **team-executor** | `team executor` | 可变 | 轻量级会话执行 |
|
||||
| **team-executor-v2** | - | 可变 | team-worker 架构执行 |
|
||||
| **team-executor** | - | 可变 | team-worker 架构执行 |
|
||||
| **team-planex** | `team planex` | 3 | 规划-执行波浪流水线 |
|
||||
| **team-iterdev** | `team iterdev` | 5 | 生成器-评论者循环迭代开发 |
|
||||
| **team-issue** | `team issue` | 6 | 问题解决流水线 |
|
||||
|
||||
@@ -21,7 +21,7 @@
|
||||
| review-cycle | 代码审查 | 3 (标准) | 是 |
|
||||
| spec-generator | 规格文档包 | 4 (完整) | 否 (链式到 plan) |
|
||||
| team-planex | Issue 批量执行 | Team | 是 |
|
||||
| team-lifecycle-v5 | 完整生命周期 | Team | 是 |
|
||||
| team-lifecycle | 完整生命周期 | Team | 是 |
|
||||
| issue pipeline | Issue 管理 | 2.5 (桥接) | 是 |
|
||||
|
||||
---
|
||||
@@ -51,7 +51,7 @@
|
||||
| spec-generator | `/ccw "specification: ..."` | study → discovery → brief → PRD → architecture → epics | 完整规格文档包 | 4 (完整) | 是 (仅文档) | workflow-plan / team-planex |
|
||||
| **团队工作流** |
|
||||
| team-planex | `/ccw "team planex: ..."` | coordinator → planner wave → executor wave | 基于 Issue 的并行执行 | Team | 是 | (完整流水线) |
|
||||
| team-lifecycle-v5 | `/ccw "team lifecycle: ..."` | spec pipeline → impl pipeline | 从规格到验证的完整生命周期 | Team | 是 | (完整生命周期) |
|
||||
| team-lifecycle | `/ccw "team lifecycle: ..."` | spec pipeline → impl pipeline | 从规格到验证的完整生命周期 | Team | 是 | (完整生命周期) |
|
||||
| team-arch-opt | (架构优化) | architecture analysis → optimization | 架构优化 | Team | 是 | (完整) |
|
||||
| **循环工作流** |
|
||||
| integration-test-cycle | `/ccw "integration test: ..."` | explore → test dev → test-fix cycle → reflection | 带迭代的集成测试 | 3 (标准) | 是 | (自迭代) |
|
||||
@@ -71,7 +71,7 @@
|
||||
| **2.5 (桥接)** | issue pipeline, rapid-to-issue | 桥接到 Issue 工作流 |
|
||||
| **3 (标准)** | workflow-plan, workflow-execute, workflow-tdd-plan, workflow-test-fix, review-cycle, debug-with-file, analyze-with-file, workflow-multi-cli-plan | 完整规划/执行、多阶段 |
|
||||
| **4 (完整)** | brainstorm, spec-generator, brainstorm-with-file, roadmap-with-file | 完整探索、规格化 |
|
||||
| **Team** | team-planex, team-lifecycle-v5, team-arch-opt | 多代理并行执行 |
|
||||
| **Team** | team-planex, team-lifecycle, team-arch-opt | 多代理并行执行 |
|
||||
| **Cycle** | integration-test-cycle, refactor-cycle | 带反思的自迭代 |
|
||||
|
||||
---
|
||||
@@ -108,7 +108,7 @@
|
||||
| review-cycle | 是 | 完整审查 + 可选修复 |
|
||||
| spec-generator | 是 (文档) | 否 (实现) |
|
||||
| team-planex | 是 | 完整团队流水线 |
|
||||
| team-lifecycle-v5 | 是 | 完整生命周期 |
|
||||
| team-lifecycle | 是 | 完整生命周期 |
|
||||
| debug-with-file | 是 | 完整调试 |
|
||||
| integration-test-cycle | 是 | 自迭代 |
|
||||
| refactor-cycle | 是 | 自迭代 |
|
||||
@@ -149,7 +149,7 @@
|
||||
| Issue 管理 | `/issue:new` → `/issue:plan` → `/issue:queue` → `/issue:execute` | issue workflow |
|
||||
| 多 Issue 批量 | `/issue:discover` → `/issue:plan --all-pending` | issue batch workflow |
|
||||
| 代码审查 | `/cli:codex-review --uncommitted` | codex review |
|
||||
| 团队协调 | `team-lifecycle-v5` 或 `team-planex` | team workflow |
|
||||
| 团队协调 | `team-lifecycle` 或 `team-planex` | team workflow |
|
||||
| TDD 开发 | `/ccw "Implement with TDD"` | tdd-plan → execute |
|
||||
| 集成测试 | `/ccw "integration test: ..."` | integration-test-cycle |
|
||||
| 技术债务 | `/ccw "refactor: ..."` | refactor-cycle |
|
||||
|
||||
@@ -9,7 +9,7 @@ CCW 提供多个支持多角色协调复杂任务的团队协作技能。
|
||||
| **team-planex** | 3 (planner + executor) | 波浪流水线(边规划边执行) | 规划和执行并行 |
|
||||
| **team-iterdev** | 5 (generator → critic → integrator → validator) | 生成器-评论者循环 | 带反馈循环的迭代开发 |
|
||||
| **team-lifecycle-v4** | 8 (spec → architect → impl → test) | 5 阶段生命周期 | 完整规范 → 实现 → 测试工作流 |
|
||||
| **team-lifecycle-v5** | 可变 (team-worker) | 内置阶段 | 最新 team-worker 架构 |
|
||||
| **team-lifecycle** | 可变 (team-worker) | 内置阶段 | 最新 team-worker 架构 |
|
||||
| **team-issue** | 6 (explorer → planner → implementer → reviewer → integrator) | 5 阶段问题解决 | 多角色问题求解 |
|
||||
| **team-testing** | 5 (strategist → generator → executor → analyst) | 4 阶段测试 | 综合测试覆盖 |
|
||||
| **team-quality-assurance** | 6 (scout → strategist → generator → executor → analyst) | 5 阶段 QA | 质量保障闭环 |
|
||||
@@ -21,9 +21,9 @@ CCW 提供多个支持多角色协调复杂任务的团队协作技能。
|
||||
| **team-tech-debt** | 6 (scanner → assessor → planner → executor → validator) | 5 阶段清理 | 技术债务识别和解决 |
|
||||
| **team-ultra-analyze** | 5 (explorer → analyst → discussant → synthesizer) | 4 阶段分析 | 深度协作代码库分析 |
|
||||
| **team-coordinate** | 可变 | 通用协调 | 通用团队协调(旧版) |
|
||||
| **team-coordinate-v2** | 可变 (team-worker) | team-worker 架构 | 现代 team-worker 协调 |
|
||||
| **team-coordinate** | 可变 (team-worker) | team-worker 架构 | 现代 team-worker 协调 |
|
||||
| **team-executor** | 可变 | 轻量级执行 | 基于会话的执行 |
|
||||
| **team-executor-v2** | 可变 (team-worker) | team-worker 执行 | 现代 team-worker 执行 |
|
||||
| **team-executor** | 可变 (team-worker) | team-worker 执行 | 现代 team-worker 执行 |
|
||||
|
||||
## 使用方法
|
||||
|
||||
@@ -45,7 +45,7 @@ CCW 提供多个支持多角色协调复杂任务的团队协作技能。
|
||||
|
||||
```javascript
|
||||
// 编程调用
|
||||
Skill(skill="team-lifecycle-v5", args="Build user authentication system")
|
||||
Skill(skill="team-lifecycle", args="Build user authentication system")
|
||||
Skill(skill="team-planex", args="Implement OAuth2 with concurrent planning")
|
||||
Skill(skill="team-quality-assurance", args="Quality audit of payment system")
|
||||
|
||||
@@ -177,7 +177,7 @@ Implementation Track: Developer → Components
|
||||
|----------|-------------------|
|
||||
| 需要并行规划和执行 | **team-planex** |
|
||||
| 带多次迭代的复杂功能 | **team-iterdev** |
|
||||
| 完整规范 → 实现 → 测试工作流 | **team-lifecycle-v5** |
|
||||
| 完整规范 → 实现 → 测试工作流 | **team-lifecycle** |
|
||||
| 问题解决 | **team-issue** |
|
||||
| 综合测试 | **team-testing** |
|
||||
| 质量审计 | **team-quality-assurance** |
|
||||
|
||||
Reference in New Issue
Block a user