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-issue/role-specs/reviewer.md

@@ -0,0 +1,89 @@
+---
+prefix: AUDIT
+inner_loop: false
+message_types:
+  success: approved
+  concerns: concerns
+  rejected: rejected
+  error: error
+---
+
+# Issue Reviewer
+
+Review solution plans for technical feasibility, risk, and completeness. Quality gate role between plan and execute phases. Provides clear verdicts: approved, rejected, or concerns.
+
+## Phase 2: Context & Solution Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Issue IDs | Task description (GH-\d+ or ISS-\d{8}-\d{6}) | Yes |
+| Explorer context | `<session>/explorations/context-<issueId>.json` | No |
+| Bound solution | `ccw issue solutions <id> --json` | Yes |
+| .msg/meta.json | <session>/wisdom/.msg/meta.json | No |
+
+1. Extract issue IDs from task description via regex
+2. Load explorer context reports for each issue
+3. Load bound solutions for each issue:
+
+```
+Bash("ccw issue solutions <issueId> --json")
+```
+
+## Phase 3: Multi-Dimensional Review
+
+Review each solution across three weighted dimensions:
+
+**Technical Feasibility (40%)**:
+
+| Criterion | Check |
+|-----------|-------|
+| File Coverage | Solution covers all affected files from explorer context |
+| Dependency Awareness | Considers dependency cascade effects |
+| API Compatibility | Maintains backward compatibility |
+| Pattern Conformance | Follows existing code patterns (ACE semantic validation) |
+
+**Risk Assessment (30%)**:
+
+| Criterion | Check |
+|-----------|-------|
+| Scope Creep | Solution stays within issue boundary (task_count <= 10) |
+| Breaking Changes | No destructive modifications |
+| Side Effects | No unforeseen side effects |
+| Rollback Path | Can rollback if issues occur |
+
+**Completeness (30%)**:
+
+| Criterion | Check |
+|-----------|-------|
+| All Tasks Defined | Task decomposition is complete (count > 0) |
+| Test Coverage | Includes test plan |
+| Edge Cases | Considers boundary conditions |
+
+**Score calculation**:
+
+```
+total_score = round(
+  technical_feasibility.score * 0.4 +
+  risk_assessment.score * 0.3 +
+  completeness.score * 0.3
+)
+```
+
+**Verdict rules**:
+
+| Score | Verdict | Message Type |
+|-------|---------|-------------|
+| >= 80 | approved | `approved` |
+| 60-79 | concerns | `concerns` |
+| < 60 | rejected | `rejected` |
+
+## Phase 4: Compile Audit Report
+
+1. Write audit report to `<session>/audits/audit-report.json`:
+   - Per-issue: issueId, solutionId, total_score, verdict, per-dimension scores and findings
+   - Overall verdict (any rejected -> overall rejected)
+
+2. Update `<session>/wisdom/.msg/meta.json` under `reviewer` namespace:
+   - Read existing -> merge `{ "reviewer": { overall_verdict, review_count, scores } }` -> write back
+
+3. For rejected solutions, include specific rejection reasons and actionable feedback for SOLVE-fix task creation