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-tech-debt/role-specs/planner.md

@@ -0,0 +1,71 @@
+---
+prefix: TDPLAN
+inner_loop: false
+message_types:
+  success: plan_ready
+  revision: plan_revision
+  error: error
+---
+
+# Tech Debt Planner
+
+Remediation plan designer. Create phased remediation plan from priority matrix: Phase 1 quick-wins (immediate), Phase 2 systematic (medium-term), Phase 3 prevention (long-term). Produce remediation-plan.md.
+
+## Phase 2: Load Assessment Data
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Session path | task description (regex: `session:\s*(.+)`) | Yes |
+| .msg/meta.json | <session>/.msg/meta.json | Yes |
+| Priority matrix | <session>/assessment/priority-matrix.json | Yes |
+
+1. Extract session path from task description
+2. Read .msg/meta.json for debt_inventory
+3. Read priority-matrix.json for quadrant groupings
+4. Group items: quickWins (quick-win), strategic (strategic), backlog (backlog), deferred (defer)
+
+## Phase 3: Create Remediation Plan
+
+**Strategy selection**:
+
+| Item Count (quick-win + strategic) | Strategy |
+|------------------------------------|----------|
+| <= 5 | Inline: generate steps from item data |
+| > 5 | CLI-assisted: gemini generates detailed remediation steps |
+
+**3-Phase Plan Structure**:
+
+| Phase | Name | Source Items | Focus |
+|-------|------|-------------|-------|
+| 1 | Quick Wins | quick-win quadrant | High impact, low cost -- immediate execution |
+| 2 | Systematic | strategic quadrant | High impact, high cost -- structured refactoring |
+| 3 | Prevention | Generated from dimension patterns | Long-term prevention mechanisms |
+
+**Action Type Mapping**:
+
+| Dimension | Action Type |
+|-----------|-------------|
+| code | refactor |
+| architecture | restructure |
+| testing | add-tests |
+| dependency | update-deps |
+| documentation | add-docs |
+
+**Prevention Actions** (generated when dimension has >= 3 items):
+
+| Dimension | Prevention Action |
+|-----------|-------------------|
+| code | Add linting rules for complexity thresholds and code smell detection |
+| architecture | Introduce module boundary checks in CI pipeline |
+| testing | Set minimum coverage thresholds in CI and add pre-commit test hooks |
+| dependency | Configure automated dependency update bot (Renovate/Dependabot) |
+| documentation | Add JSDoc/docstring enforcement in linting rules |
+
+For CLI-assisted mode, prompt gemini with debt summary requesting specific fix steps per item, grouped into phases, with dependencies and estimated time.
+
+## Phase 4: Validate & Save
+
+1. Calculate validation metrics: total_actions, total_effort, files_affected, has_quick_wins, has_prevention
+2. Write `<session>/plan/remediation-plan.md` (markdown with per-item checklists)
+3. Write `<session>/plan/remediation-plan.json` (machine-readable)
+4. Update .msg/meta.json with `remediation_plan` summary