claude-code-workflow 7.2.23 → 7.2.24

package/.codex/skills/team-ux-improve/roles/scanner/role.md

@@ -1,93 +1,93 @@
----
-role: scanner
-prefix: SCAN
-inner_loop: false
-message_types: [state_update]
----
-
-# UI Scanner
-
-Scan UI components to identify interaction issues: unresponsive buttons, missing feedback mechanisms, state not refreshing.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Project path | Task description CONTEXT | Yes |
-| Framework | Task description CONTEXT | Yes |
-| Scan scope | Task description CONSTRAINTS | Yes |
-
-1. Extract session path and project path from task description
-2. Detect framework from project structure:
-
-| Signal | Framework |
-|--------|-----------|
-| package.json has "react" | React |
-| package.json has "vue" | Vue |
-| *.tsx files present | React |
-| *.vue files present | Vue |
-
-3. Build file pattern list for scanning:
-   - React: `**/*.tsx`, `**/*.jsx`, `**/use*.ts`
-   - Vue: `**/*.vue`, `**/composables/*.ts`
-
-### Wisdom Input
-
-1. Read `<session>/wisdom/anti-patterns/common-ux-pitfalls.md` if available
-2. Use anti-patterns to identify known UX issues during scanning
-3. Check `<session>/wisdom/patterns/ui-feedback.md` for expected feedback patterns
-
-### Complex Analysis (use CLI)
-
-For large projects with many components:
-
-```
-Bash(`ccw cli -p "PURPOSE: Discover all UI components with user interactions
-CONTEXT: @<project-path>/**/*.tsx @<project-path>/**/*.vue
-EXPECTED: Component list with interaction types (click, submit, input, select)
-CONSTRAINTS: Focus on interactive components only" --tool gemini --mode analysis`)
-```
-
-## Phase 3: Component Scanning
-
-Scan strategy:
-
-| Category | Detection Pattern | Severity |
-|----------|-------------------|----------|
-| Unresponsive actions | onClick/\@click without async handling or error catching | High |
-| Missing loading state | Form submit without isLoading/loading ref | High |
-| State not refreshing | Array.splice/push without reactive reassignment | High |
-| Missing error feedback | try/catch without error state or user notification | Medium |
-| Missing success feedback | API call without success confirmation | Medium |
-| No empty state | Data list without empty state placeholder | Low |
-| Input without validation | Form input without validation rules | Low |
-| Missing file selector | Text input for file/folder path without picker | Medium |
-
-For each component file:
-1. Read file content
-2. Scan for interaction patterns using Grep
-3. Check for feedback mechanisms (loading, error, success states)
-4. Check state update patterns (mutation vs reactive)
-5. Record issues with file:line references
-
-## Phase 4: Issue Report Generation
-
-1. Classify issues by severity (High/Medium/Low)
-2. Group by category (unresponsive, missing feedback, state issues, input UX)
-3. Generate structured report and write to `<session>/artifacts/scan-report.md`
-4. Share state via team_msg:
-   ```
-   team_msg(operation="log", session_id=<session-id>, from="scanner",
-            type="state_update", data={
-              total_issues: <count>,
-              high: <count>, medium: <count>, low: <count>,
-              categories: [<category-list>],
-              scanned_files: <count>
-            })
-   ```
-
-### Wisdom Contribution
-
-If novel UX issues discovered that aren't in anti-patterns:
-1. Write findings to `<session>/wisdom/contributions/scanner-issues-<timestamp>.md`
-2. Format: Issue description, detection criteria, affected components
+---
+role: scanner
+prefix: SCAN
+inner_loop: false
+message_types: [state_update]
+---
+
+# UI Scanner
+
+Scan UI components to identify interaction issues: unresponsive buttons, missing feedback mechanisms, state not refreshing.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Project path | Task description CONTEXT | Yes |
+| Framework | Task description CONTEXT | Yes |
+| Scan scope | Task description CONSTRAINTS | Yes |
+
+1. Extract session path and project path from task description
+2. Detect framework from project structure:
+
+| Signal | Framework |
+|--------|-----------|
+| package.json has "react" | React |
+| package.json has "vue" | Vue |
+| *.tsx files present | React |
+| *.vue files present | Vue |
+
+3. Build file pattern list for scanning:
+   - React: `**/*.tsx`, `**/*.jsx`, `**/use*.ts`
+   - Vue: `**/*.vue`, `**/composables/*.ts`
+
+### Wisdom Input
+
+1. Read `<session>/wisdom/anti-patterns/common-ux-pitfalls.md` if available
+2. Use anti-patterns to identify known UX issues during scanning
+3. Check `<session>/wisdom/patterns/ui-feedback.md` for expected feedback patterns
+
+### Complex Analysis (use CLI)
+
+For large projects with many components:
+
+```
+Bash(`ccw cli -p "PURPOSE: Discover all UI components with user interactions
+CONTEXT: @<project-path>/**/*.tsx @<project-path>/**/*.vue
+EXPECTED: Component list with interaction types (click, submit, input, select)
+CONSTRAINTS: Focus on interactive components only" --tool gemini --mode analysis`)
+```
+
+## Phase 3: Component Scanning
+
+Scan strategy:
+
+| Category | Detection Pattern | Severity |
+|----------|-------------------|----------|
+| Unresponsive actions | onClick/\@click without async handling or error catching | High |
+| Missing loading state | Form submit without isLoading/loading ref | High |
+| State not refreshing | Array.splice/push without reactive reassignment | High |
+| Missing error feedback | try/catch without error state or user notification | Medium |
+| Missing success feedback | API call without success confirmation | Medium |
+| No empty state | Data list without empty state placeholder | Low |
+| Input without validation | Form input without validation rules | Low |
+| Missing file selector | Text input for file/folder path without picker | Medium |
+
+For each component file:
+1. Read file content
+2. Scan for interaction patterns using Grep
+3. Check for feedback mechanisms (loading, error, success states)
+4. Check state update patterns (mutation vs reactive)
+5. Record issues with file:line references
+
+## Phase 4: Issue Report Generation
+
+1. Classify issues by severity (High/Medium/Low)
+2. Group by category (unresponsive, missing feedback, state issues, input UX)
+3. Generate structured report and write to `<session>/artifacts/scan-report.md`
+4. Share state via team_msg:
+   ```
+   team_msg(operation="log", session_id=<session-id>, from="scanner",
+            type="state_update", data={
+              total_issues: <count>,
+              high: <count>, medium: <count>, low: <count>,
+              categories: [<category-list>],
+              scanned_files: <count>
+            })
+   ```
+
+### Wisdom Contribution
+
+If novel UX issues discovered that aren't in anti-patterns:
+1. Write findings to `<session>/wisdom/contributions/scanner-issues-<timestamp>.md`
+2. Format: Issue description, detection criteria, affected components

package/.codex/skills/team-ux-improve/roles/tester/role.md

@@ -1,84 +1,84 @@
----
-role: tester
-prefix: TEST
-inner_loop: false
-message_types: [state_update]
----
-
-# Test Engineer
-
-Generate and run tests to verify fixes (loading states, error handling, state updates).
-
-## Phase 2: Environment Detection
-
-1. Detect test framework from project files:
-
-| Signal | Framework |
-|--------|-----------|
-| package.json has "jest" | Jest |
-| package.json has "vitest" | Vitest |
-| package.json has "@testing-library/react" | React Testing Library |
-| package.json has "@vue/test-utils" | Vue Test Utils |
-
-2. Get changed files from implementer state:
-   ```
-   team_msg(operation="get_state", session_id=<session-id>, role="implementer")
-   ```
-
-3. Load test strategy from design guide
-
-### Wisdom Input
-
-1. Read `<session>/wisdom/anti-patterns/common-ux-pitfalls.md` for common issues to test
-2. Read `<session>/wisdom/patterns/ui-feedback.md` for expected feedback behaviors to verify
-3. Use wisdom to design comprehensive test cases covering known edge cases
-
-## Phase 3: Test Generation & Execution
-
-### Test Generation
-
-For each modified file, generate test cases covering loading states, error handling, state updates, and accessibility.
-
-### Test Execution
-
-Iterative test-fix cycle (max 5 iterations):
-
-1. Run tests: `npm test` or `npm run test:unit`
-2. Parse results -> calculate pass rate
-3. If pass rate >= 95% -> exit (success)
-4. If pass rate < 95% and iterations < 5:
-   - Analyze failures
-   - Use CLI to generate fixes:
-     ```
-     Bash(`ccw cli -p "PURPOSE: Fix test failures
-     CONTEXT: @<test-file> @<source-file>
-     EXPECTED: Fixed code that passes tests
-     CONSTRAINTS: Maintain existing functionality" --tool gemini --mode write`)
-     ```
-   - Increment iteration counter
-   - Loop to step 1
-5. If iterations >= 5 -> send fix_required message
-
-## Phase 4: Test Report
-
-### Wisdom Contribution
-
-If new edge cases or test patterns discovered:
-1. Write test findings to `<session>/wisdom/contributions/tester-edge-cases-<timestamp>.md`
-2. Format: Edge case description, test scenario, expected behavior, actual behavior
-
-Write report to `<session>/artifacts/test-report.md`.
-
-Share state via team_msg:
-```
-team_msg(operation="log", session_id=<session-id>, from="tester",
-         type="state_update", data={
-           total_tests: <count>,
-           passed: <count>,
-           failed: <count>,
-           pass_rate: <percentage>,
-           fix_iterations: <count>
-         })
-```
-
-If pass rate < 95%, send fix_required message to coordinator.
+---
+role: tester
+prefix: TEST
+inner_loop: false
+message_types: [state_update]
+---
+
+# Test Engineer
+
+Generate and run tests to verify fixes (loading states, error handling, state updates).
+
+## Phase 2: Environment Detection
+
+1. Detect test framework from project files:
+
+| Signal | Framework |
+|--------|-----------|
+| package.json has "jest" | Jest |
+| package.json has "vitest" | Vitest |
+| package.json has "@testing-library/react" | React Testing Library |
+| package.json has "@vue/test-utils" | Vue Test Utils |
+
+2. Get changed files from implementer state:
+   ```
+   team_msg(operation="get_state", session_id=<session-id>, role="implementer")
+   ```
+
+3. Load test strategy from design guide
+
+### Wisdom Input
+
+1. Read `<session>/wisdom/anti-patterns/common-ux-pitfalls.md` for common issues to test
+2. Read `<session>/wisdom/patterns/ui-feedback.md` for expected feedback behaviors to verify
+3. Use wisdom to design comprehensive test cases covering known edge cases
+
+## Phase 3: Test Generation & Execution
+
+### Test Generation
+
+For each modified file, generate test cases covering loading states, error handling, state updates, and accessibility.
+
+### Test Execution
+
+Iterative test-fix cycle (max 5 iterations):
+
+1. Run tests: `npm test` or `npm run test:unit`
+2. Parse results -> calculate pass rate
+3. If pass rate >= 95% -> exit (success)
+4. If pass rate < 95% and iterations < 5:
+   - Analyze failures
+   - Use CLI to generate fixes:
+     ```
+     Bash(`ccw cli -p "PURPOSE: Fix test failures
+     CONTEXT: @<test-file> @<source-file>
+     EXPECTED: Fixed code that passes tests
+     CONSTRAINTS: Maintain existing functionality" --tool gemini --mode write`)
+     ```
+   - Increment iteration counter
+   - Loop to step 1
+5. If iterations >= 5 -> send fix_required message
+
+## Phase 4: Test Report
+
+### Wisdom Contribution
+
+If new edge cases or test patterns discovered:
+1. Write test findings to `<session>/wisdom/contributions/tester-edge-cases-<timestamp>.md`
+2. Format: Edge case description, test scenario, expected behavior, actual behavior
+
+Write report to `<session>/artifacts/test-report.md`.
+
+Share state via team_msg:
+```
+team_msg(operation="log", session_id=<session-id>, from="tester",
+         type="state_update", data={
+           total_tests: <count>,
+           passed: <count>,
+           failed: <count>,
+           pass_rate: <percentage>,
+           fix_iterations: <count>
+         })
+```
+
+If pass rate < 95%, send fix_required message to coordinator.

package/.codex/skills/team-ux-improve/specs/pipelines.md

@@ -1,54 +1,54 @@
-# Pipeline Definitions
-
-UX improvement pipeline modes and task registry.
-
-## Pipeline Modes
-
-| Mode | Description | Task Chain |
-|------|-------------|------------|
-| standard | Full UX improvement pipeline | SCAN-001 -> DIAG-001 -> DESIGN-001 -> IMPL-001 -> TEST-001 |
-
-## Standard Pipeline Task Registry
-
-| Task ID | Role | blockedBy | Inner Loop | Description |
-|---------|------|-----------|------------|-------------|
-| SCAN-001 | scanner | [] | false | Scan UI components for interaction issues (unresponsive buttons, missing feedback, state problems) |
-| DIAG-001 | diagnoser | [SCAN-001] | false | Root cause diagnosis with fix recommendations |
-| DESIGN-001 | designer | [DIAG-001] | false | Feedback mechanism and state management solution design |
-| IMPL-001 | implementer | [DESIGN-001] | true | Code implementation with proper state handling |
-| TEST-001 | tester | [IMPL-001] | false | Test generation and validation (pass rate >= 95%, max 5 iterations) |
-
-## Checkpoints
-
-| Checkpoint | Trigger | Condition | Action |
-|------------|---------|-----------|--------|
-| Pipeline complete | TEST-001 completes | All tasks done | Coordinator Phase 5: wisdom consolidation + completion action |
-
-## Test Iteration Behavior
-
-| Condition | Action |
-|-----------|--------|
-| pass_rate >= 95% | Pipeline complete |
-| pass_rate < 95% AND iterations < 5 | Tester generates fixes, re-runs (inner loop within TEST-001) |
-| pass_rate < 95% AND iterations >= 5 | Accept current state, report to coordinator |
-
-## Output Artifacts
-
-| Task | Output Path |
-|------|-------------|
-| SCAN-001 | <session>/artifacts/scan-report.md |
-| DIAG-001 | <session>/artifacts/diagnosis.md |
-| DESIGN-001 | <session>/artifacts/design-guide.md |
-| IMPL-001 | <session>/artifacts/fixes/ |
-| TEST-001 | <session>/artifacts/test-report.md |
-
-## Wisdom System
-
-Workers contribute learnings to `<session>/wisdom/contributions/`. On pipeline completion, coordinator asks user to merge approved contributions to permanent wisdom at `~  or <project>/.claude/skills/team-ux-improve/wisdom/`.
-
-| Directory | Purpose |
-|-----------|---------|
-| wisdom/principles/ | Core UX principles |
-| wisdom/patterns/ | Solution patterns (ui-feedback, state-management) |
-| wisdom/anti-patterns/ | Issues to avoid (common-ux-pitfalls) |
-| wisdom/contributions/ | Session worker contributions (pending review) |
+# Pipeline Definitions
+
+UX improvement pipeline modes and task registry.
+
+## Pipeline Modes
+
+| Mode | Description | Task Chain |
+|------|-------------|------------|
+| standard | Full UX improvement pipeline | SCAN-001 -> DIAG-001 -> DESIGN-001 -> IMPL-001 -> TEST-001 |
+
+## Standard Pipeline Task Registry
+
+| Task ID | Role | blockedBy | Inner Loop | Description |
+|---------|------|-----------|------------|-------------|
+| SCAN-001 | scanner | [] | false | Scan UI components for interaction issues (unresponsive buttons, missing feedback, state problems) |
+| DIAG-001 | diagnoser | [SCAN-001] | false | Root cause diagnosis with fix recommendations |
+| DESIGN-001 | designer | [DIAG-001] | false | Feedback mechanism and state management solution design |
+| IMPL-001 | implementer | [DESIGN-001] | true | Code implementation with proper state handling |
+| TEST-001 | tester | [IMPL-001] | false | Test generation and validation (pass rate >= 95%, max 5 iterations) |
+
+## Checkpoints
+
+| Checkpoint | Trigger | Condition | Action |
+|------------|---------|-----------|--------|
+| Pipeline complete | TEST-001 completes | All tasks done | Coordinator Phase 5: wisdom consolidation + completion action |
+
+## Test Iteration Behavior
+
+| Condition | Action |
+|-----------|--------|
+| pass_rate >= 95% | Pipeline complete |
+| pass_rate < 95% AND iterations < 5 | Tester generates fixes, re-runs (inner loop within TEST-001) |
+| pass_rate < 95% AND iterations >= 5 | Accept current state, report to coordinator |
+
+## Output Artifacts
+
+| Task | Output Path |
+|------|-------------|
+| SCAN-001 | <session>/artifacts/scan-report.md |
+| DIAG-001 | <session>/artifacts/diagnosis.md |
+| DESIGN-001 | <session>/artifacts/design-guide.md |
+| IMPL-001 | <session>/artifacts/fixes/ |
+| TEST-001 | <session>/artifacts/test-report.md |
+
+## Wisdom System
+
+Workers contribute learnings to `<session>/wisdom/contributions/`. On pipeline completion, coordinator asks user to merge approved contributions to permanent wisdom at `~  or <project>/.claude/skills/team-ux-improve/wisdom/`.
+
+| Directory | Purpose |
+|-----------|---------|
+| wisdom/principles/ | Core UX principles |
+| wisdom/patterns/ | Solution patterns (ui-feedback, state-management) |
+| wisdom/anti-patterns/ | Issues to avoid (common-ux-pitfalls) |
+| wisdom/contributions/ | Session worker contributions (pending review) |

package/README.md

@@ -95,6 +95,7 @@ If you use **Codex CLI** with the `.codex/skills/` workflow skills, add these re
 [features]
 default_mode_request_user_input = true   # Enable request_user_input tool for interactive confirmations
 multi_agent = true                       # Enable multi-agent coordination (spawn_agent, wait, etc.)
+multi_agent_v2 = true                    # Enable v4 agent API (fork_context, task_name, send_message, assign_task, list_agents)
 enable_fanout = true                     # Enable spawn_agents_on_csv for parallel wave execution
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-code-workflow",
-  "version": "7.2.23",
+  "version": "7.2.24",
   "description": "JSON-driven multi-agent development framework with intelligent CLI orchestration (Gemini/Qwen/Codex), context-first architecture, and automated workflow execution",
   "type": "module",
   "main": "ccw/dist/index.js",