mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-06 16:31:12 +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:
@@ -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 | 问题解决流水线 |
|
||||
|
||||
Reference in New Issue
Block a user