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.
2026-03-06 16:31:12 +08:00 · 2026-03-04 11:07:48 +08:00
parent 5e96722c09
commit ffd5282932
132 changed files with 2938 additions and 18916 deletions
--- a/.claude/skills/team-ultra-analyze/SKILL.md
+++ b/.claude/skills/team-ultra-analyze/SKILL.md
@@ -11,21 +11,23 @@ Deep collaborative analysis team skill. Splits monolithic analysis into 5-role c
 ## Architecture

 ```
-+-------------------------------------------------------------+
-|  Skill(skill="team-ultra-analyze")                          |
-|  args="topic description" or args="--role=xxx"              |
-+----------------------------+--------------------------------+
-                             | Role Router
-          +---- --role present? ----+
-          | NO                      | YES
-          v                         v
-   Orchestration Mode         Role Dispatch
-   (auto -> coordinator)     (route to role.md)
-          |
-    +-----+------+----------+-----------+
-    v            v          v           v           v
- coordinator  explorer   analyst   discussant  synthesizer
-              EXPLORE-*  ANALYZE-*  DISCUSS-*   SYNTH-*
+---------------------------------------------------+
+|  Skill(skill="team-ultra-analyze")                 |
+|  args="<topic-description>"                        |
+-------------------+-------------------------------+
+                    |
+         Orchestration Mode (auto -> coordinator)
+                    |
+              Coordinator (inline)
+              Phase 0-5 orchestration
+                    |
+    +-------+-------+-------+-------+
+    v       v       v       v
+ [tw]    [tw]    [tw]    [tw]
+explor- analy-  discu-  synthe-
+er      st      ssant   sizer
+
+(tw) = team-worker agent
 ```

 ## Command Architecture
@@ -65,13 +67,13 @@ Parse `$ARGUMENTS` to extract `--role` and optional `--agent-name`. If `--role`

 ### Role Registry

-| Role | File | Task Prefix | Type | Compact |
-|------|------|-------------|------|---------|
-| coordinator | [roles/coordinator/role.md](roles/coordinator/role.md) | (none) | orchestrator | **compress: must re-read** |
-| explorer | [roles/explorer/role.md](roles/explorer/role.md) | EXPLORE-* | parallel worker | compress: must re-read |
-| analyst | [roles/analyst/role.md](roles/analyst/role.md) | ANALYZE-* | parallel worker | compress: must re-read |
-| discussant | [roles/discussant/role.md](roles/discussant/role.md) | DISCUSS-* | pipeline | compress: must re-read |
-| synthesizer | [roles/synthesizer/role.md](roles/synthesizer/role.md) | SYNTH-* | pipeline | compress: must re-read |
+| Role | Spec | Task Prefix | Inner Loop |
+|------|------|-------------|------------|
+| coordinator | [roles/coordinator/role.md](roles/coordinator/role.md) | (none) | - |
+| explorer | [role-specs/explorer.md](role-specs/explorer.md) | EXPLORE-* | false |
+| analyst | [role-specs/analyst.md](role-specs/analyst.md) | ANALYZE-* | false |
+| discussant | [role-specs/discussant.md](role-specs/discussant.md) | DISCUSS-* | false |
+| synthesizer | [role-specs/synthesizer.md](role-specs/synthesizer.md) | SYNTH-* | false |

 > **COMPACT PROTECTION**: Role files are execution documents, not reference material. When context compression occurs and role instructions are reduced to summaries, you **must immediately `Read` the corresponding role.md to reload before continuing execution**. Never execute any Phase based on compressed summaries alone.

@@ -338,51 +340,43 @@ Beat  1          2          3         3a...       4

 ## Coordinator Spawn Template

-When coordinator spawns workers, use background mode (Spawn-and-Stop pattern). The coordinator determines the depth (number of parallel agents) based on selected perspectives.
+### v5 Worker Spawn (all roles)

-**Phase 1 - Spawn Explorers**: Create depth explorer agents in parallel (EXPLORE-1 through EXPLORE-depth). Each explorer receives its assigned perspective/domain and agent name for task matching. All spawned with run_in_background:true. Coordinator stops after spawning and waits for callbacks.
+When coordinator spawns workers, use `team-worker` agent with role-spec path. The coordinator determines depth (number of parallel agents) based on selected perspectives.

-**Phase 2 - Spawn Analysts**: After all explorers complete, create depth analyst agents in parallel (ANALYZE-1 through ANALYZE-depth). Each analyst receives its assigned perspective matching the corresponding explorer. All spawned with run_in_background:true. Coordinator stops.
+**Phase 1 - Spawn Explorers**: Create depth explorer team-worker agents in parallel (EXPLORE-1 through EXPLORE-depth). Each receives its assigned perspective/domain and agent name for task matching.

-**Phase 3 - Spawn Discussant**: After all analysts complete, create 1 discussant. It processes all analysis results and presents findings to user. Coordinator stops.
+**Phase 2 - Spawn Analysts**: After all explorers complete, create depth analyst team-worker agents in parallel (ANALYZE-1 through ANALYZE-depth).

-**Phase 3a - Discussion Loop** (Deep mode only): Based on user feedback, coordinator may create additional ANALYZE-fix and DISCUSS tasks. Loop continues until user is satisfied or 5 rounds reached.
+**Phase 3 - Spawn Discussant**: After all analysts complete, create 1 discussant. Coordinator stops.

-**Phase 4 - Spawn Synthesizer**: After final discussion round, create 1 synthesizer. It integrates all explorations, analyses, and discussions into final conclusions. Coordinator stops.
+**Phase 3a - Discussion Loop** (Deep mode only): Based on user feedback, coordinator may create additional ANALYZE-fix and DISCUSS tasks.

-**Quick mode exception**: When depth=1, spawn single explorer, single analyst, single discussant, single synthesizer -- all as simple agents without numbered suffixes.
+**Phase 4 - Spawn Synthesizer**: After final discussion round, create 1 synthesizer.

-**Single spawn example** (worker template used for all roles):
+**Quick mode exception**: When depth=1, spawn single explorer, single analyst, single discussant, single synthesizer without numbered suffixes.
+
+**Single spawn template** (worker template used for all roles):

 ```
 Task({
-  subagent_type: "general-purpose",
+  subagent_type: "team-worker",
  description: "Spawn <role> worker",
-  team_name: <team-name>,
+  team_name: "ultra-analyze",
  name: "<agent-name>",
  run_in_background: true,
-  prompt: `You are team "<team-name>" <ROLE> (<agent-name>).
-Your agent name is "<agent-name>", use it for task discovery owner matching.
+  prompt: `## Role Assignment
+role: <role>
+role_spec: .claude/skills/team-ultra-analyze/role-specs/<role>.md
+session: <session-folder>
+session_id: <session-id>
+team_name: ultra-analyze
+requirement: <topic-description>
+agent_name: <agent-name>
+inner_loop: false

-## Primary Instruction
-All work must be executed by calling Skill for role definition:
-Skill(skill="team-ultra-analyze", args="--role=<role> --agent-name=<agent-name>")
-
-Current topic: <task-description>
-Session: <session-folder>
-
-## Role Rules
- Only process <PREFIX>-* tasks where owner === "<agent-name>"
- All output prefixed with [<role>] identifier
- Communicate only with coordinator
- Do not use TaskCreate for other roles
- Call mcp__ccw-tools__team_msg before every SendMessage
-
-## Workflow
-1. Call Skill -> load role definition and execution logic
-2. Execute role.md 5-Phase process
-3. team_msg + SendMessage result to coordinator
-4. TaskUpdate completed -> check next task`
+Read role_spec file to load Phase 2-4 domain instructions.
+Execute built-in Phase 1 (task discovery, owner=<agent-name>) -> role-spec Phase 2-4 -> built-in Phase 5 (report).`
 })
 ```

@@ -419,6 +413,31 @@ Session: <session-folder>
 |   +-- issues.md
 ```

+## Completion Action
+
+When the pipeline completes (all tasks done, coordinator Phase 5):
+
+```
+AskUserQuestion({
+  questions: [{
+    question: "Ultra-Analyze pipeline complete. What would you like to do?",
+    header: "Completion",
+    multiSelect: false,
+    options: [
+      { label: "Archive & Clean (Recommended)", description: "Archive session, clean up tasks and team resources" },
+      { label: "Keep Active", description: "Keep session active for follow-up work or inspection" },
+      { label: "Export Results", description: "Export deliverables to a specified location, then clean" }
+    ]
+  }]
+})
+```
+
+| Choice | Action |
+|--------|--------|
+| Archive & Clean | Update session status="completed" -> TeamDelete(ultra-analyze) -> output final summary |
+| Keep Active | Update session status="paused" -> output resume instructions: `Skill(skill="team-ultra-analyze", args="resume")` |
+| Export Results | AskUserQuestion for target path -> copy deliverables -> Archive & Clean |
+
 ## Session Resume

 Coordinator supports `--resume` / `--continue` for interrupted sessions: