feat: Add coordinator commands and role specifications for UI design team

- Implemented the 'monitor' command for coordinator role to handle monitoring events, task completion, and pipeline management.
- Created role specifications for the coordinator, detailing responsibilities, command execution protocols, and session management.
- Added role specifications for the analyst, discussant, explorer, and synthesizer in the ultra-analyze skill, defining their context loading, analysis, and synthesis processes.

.claude/skills/team-planex/SKILL.md

@@ -260,7 +260,7 @@ if (autoYes) {
 
 ```
 .workflow/.team/PEX-{slug}-{date}/
-├── team-session.json           # Session state
+├── .msg/meta.json           # Session state
 ├── artifacts/
 │   └── solutions/              # Planner solution output per issue
 │       ├── {issueId-1}.json
@@ -270,7 +270,8 @@ if (autoYes) {
 │   ├── decisions.md
 │   ├── conventions.md
 │   └── issues.md
-└── shared-memory.json          # Cross-role state
+├── .msg/messages.jsonl          # Team message bus
+└── .msg/meta.json               # Session metadata
 ```
 
 ---
@@ -279,8 +280,9 @@ if (autoYes) {
 
 每次 SendMessage 前，先调用 `mcp__ccw-tools__team_msg` 记录：
 
-- 参数: operation="log", team=`<session-id>`, from=`<role>`, to=`<target-role>`, type=`<type>`, summary="[`<role>`] `<summary>`"
-- **注意**: `team` 必须是 **session ID** (如 `PEX-project-2026-02-27`), 不是 team name.
+- 参数: operation="log", session_id=`<session-id>`, from=`<role>`, type=`<type>`, data={ref: "`<artifact-path>`"}
+- `to` and `summary` auto-defaulted -- do NOT specify explicitly
+- **CLI fallback**: `ccw team log --session-id <session-id> --from <role> --type <type> --json`
 
 **Message types by role**:
 

.claude/skills/team-planex/role-specs/executor.md

@@ -88,8 +88,7 @@ ccw issue update <issueId> --status completed
 
 ### Report
 
-Send `impl_complete` message to coordinator via team_msg + SendMessage:
-- summary: `[executor] Implemented <issueId>: <title>`
+Send `impl_complete` message to coordinator via team_msg + SendMessage.
 
 ## Boundaries
 

.claude/skills/team-planex/role-specs/planner.md

@@ -88,7 +88,6 @@ InnerLoop: true`,
 
 Send message via team_msg + SendMessage to coordinator:
 - type: `issue_ready`
-- summary: `[planner] Solution ready for <issueId>`
 
 ### 3f. Continue Loop
 

.claude/skills/team-planex/roles/coordinator/commands/monitor.md

@@ -16,7 +16,7 @@ Event-driven pipeline coordination with Spawn-and-Stop pattern. Three wake-up so
 
 | Input | Source | Required |
 |-------|--------|----------|
-| Session file | `<session-folder>/team-session.json` | Yes |
+| Session file | `<session-folder>/.msg/meta.json` | Yes |
 | Task list | `TaskList()` | Yes |
 | Active workers | session.active_workers[] | Yes |
 

.claude/skills/team-planex/roles/coordinator/role.md

@@ -14,7 +14,7 @@ Orchestrate the team-planex pipeline: parse input, create team, dispatch tasks,
 - Create team and initialize session directory
 - Dispatch tasks via `commands/dispatch.md`
 - Monitor progress via `commands/monitor.md` with Spawn-and-Stop pattern
-- Maintain session state (team-session.json)
+- Maintain session state (.msg/meta.json)
 
 ### MUST NOT
 - Execute planning or implementation work directly (delegate to workers)
@@ -62,7 +62,7 @@ For callback/check/resume: load `commands/monitor.md` and execute the appropriat
 
 ## Phase 0: Session Resume Check
 
-1. Scan `.workflow/.team/PEX-*/team-session.json` for sessions with status "active" or "paused"
+1. Scan `.workflow/.team/PEX-*/.msg/meta.json` for sessions with status "active" or "paused"
 2. No sessions found -> proceed to Phase 1
 3. Single session found -> resume (Session Reconciliation)
 4. Multiple sessions -> AskUserQuestion for selection
@@ -95,7 +95,7 @@ For callback/check/resume: load `commands/monitor.md` and execute the appropriat
 3. Create subdirectories: `artifacts/solutions/`, `wisdom/`
 4. Call `TeamCreate` with team name (default: "planex")
 5. Initialize wisdom files (learnings.md, decisions.md, conventions.md, issues.md)
-6. Write team-session.json:
+6. Write .msg/meta.json:
 
 ```
 {