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-ultra-analyze/role-specs/analyst.md

@@ -0,0 +1,90 @@
+---
+prefix: ANALYZE
+inner_loop: false
+additional_prefixes: [ANALYZE-fix]
+subagents: []
+message_types:
+  success: analysis_ready
+  error: error
+---
+
+# Deep Analyst
+
+Perform deep multi-perspective analysis on exploration results via CLI tools. Generate structured insights, discussion points, and recommendations with confidence levels.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task description | From task subject/description | Yes |
+| Session path | Extracted from task description | Yes |
+| Exploration results | `<session>/explorations/*.json` | Yes |
+
+1. Extract session path, topic, perspective, dimensions from task description
+2. Detect direction-fix mode: `type:\s*direction-fix` with `adjusted_focus:\s*(.+)`
+3. Load corresponding exploration results:
+
+| Condition | Source |
+|-----------|--------|
+| Direction fix | Read ALL exploration files, merge context |
+| Normal ANALYZE-N | Read exploration matching number N |
+| Fallback | Read first available exploration file |
+
+4. Select CLI tool by perspective:
+
+| Perspective | CLI Tool | Rule Template |
+|-------------|----------|---------------|
+| technical | gemini | analysis-analyze-code-patterns |
+| architectural | claude | analysis-review-architecture |
+| business | codex | analysis-analyze-code-patterns |
+| domain_expert | gemini | analysis-analyze-code-patterns |
+| direction-fix (any) | gemini | analysis-diagnose-bug-root-cause |
+
+## Phase 3: Deep Analysis via CLI
+
+Build analysis prompt with exploration context:
+
+```
+PURPOSE: <Normal: "Deep analysis of '<topic>' from <perspective> perspective">
+         <Fix: "Supplementary analysis with adjusted focus on '<adjusted_focus>'">
+Success: Actionable insights with confidence levels and evidence references
+
+PRIOR EXPLORATION CONTEXT:
+- Key files: <top 5-8 files from exploration>
+- Patterns found: <top 3-5 patterns>
+- Key findings: <top 3-5 findings>
+
+TASK:
+- <perspective-specific analysis tasks>
+- Generate structured findings with confidence levels (high/medium/low)
+- Identify discussion points requiring user input
+- List open questions needing further exploration
+
+MODE: analysis
+CONTEXT: @**/* | Topic: <topic>
+EXPECTED: Structured analysis with: key_insights, key_findings, discussion_points, open_questions, recommendations
+CONSTRAINTS: Focus on <perspective> perspective | <dimensions>
+```
+
+Execute: `ccw cli -p "<prompt>" --tool <cli-tool> --mode analysis --rule <rule>`
+
+## Phase 4: Result Aggregation
+
+Write analysis output to `<session>/analyses/analysis-<num>.json`:
+
+```json
+{
+  "perspective": "<perspective>",
+  "dimensions": ["<dim1>", "<dim2>"],
+  "is_direction_fix": false,
+  "key_insights": [{"insight": "...", "confidence": "high", "evidence": "file:line"}],
+  "key_findings": [{"finding": "...", "file_ref": "...", "impact": "..."}],
+  "discussion_points": ["..."],
+  "open_questions": ["..."],
+  "recommendations": [{"action": "...", "rationale": "...", "priority": "high"}],
+  "_metadata": {"cli_tool": "...", "cli_rule": "...", "perspective": "...", "timestamp": "..."}
+}
+```
+
+Update `<session>/wisdom/.msg/meta.json` under `analyst` namespace:
+- Read existing -> merge `{ "analyst": { perspective, insight_count, finding_count, is_direction_fix } }` -> write back