claude-code-workflow 7.2.23 → 7.2.25

package/.codex/skills/team-issue/roles/reviewer/role.md

@@ -1,86 +1,86 @@
----
-role: reviewer
-prefix: AUDIT
-inner_loop: false
-message_types: [approved, concerns, rejected, 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 |
-| wisdom meta | <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
+---
+role: reviewer
+prefix: AUDIT
+inner_loop: false
+message_types: [approved, concerns, rejected, 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 |
+| wisdom meta | <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

package/.codex/skills/team-issue/specs/pipelines.md

@@ -1,124 +1,124 @@
-# Pipeline Definitions — team-issue
-
-## Available Pipelines
-
-### Quick Pipeline (4 beats, strictly serial)
-
-```
-EXPLORE-001 → SOLVE-001 → MARSHAL-001 → BUILD-001
-[explorer]    [planner]   [integrator]  [implementer]
-```
-
-Use when: 1-2 simple issues, no high-priority (priority < 4).
-
-### Full Pipeline (5 beats, with review gate)
-
-```
-EXPLORE-001 → SOLVE-001 → AUDIT-001 ─┬─(approved/concerns)→ MARSHAL-001 → BUILD-001
-[explorer]    [planner]   [reviewer]  │
-                                      └─(rejected, round<2)→ SOLVE-fix-001 → AUDIT-002 → MARSHAL-001 → BUILD-001
-```
-
-Use when: 1-4 issues with high-priority, or 3-4 issues regardless of priority.
-
-### Batch Pipeline (parallel windows)
-
-```
-[EXPLORE-001..N](parallel, max 5) → [SOLVE-001..N](sequential) → AUDIT-001 → MARSHAL-001 → [BUILD-001..M](parallel, max 3, deferred)
-```
-
-Use when: 5+ issues.
-
-Note: BUILD tasks are created dynamically after MARSHAL completes and execution-queue.json is available.
-
-## Task Metadata Registry
-
-| Task ID | Role | Phase | Dependencies | Description |
-|---------|------|-------|-------------|-------------|
-| EXPLORE-001 | explorer | explore | (none) | Context analysis and impact assessment |
-| EXPLORE-002..N | explorer | explore | (none) | Parallel exploration (Batch mode only, max 5) |
-| SOLVE-001 | planner | plan | EXPLORE-001 (or all EXPLORE-*) | Solution design and task decomposition |
-| SOLVE-002..N | planner | plan | all EXPLORE-* | Parallel solution design (Batch mode only) |
-| AUDIT-001 | reviewer | review | SOLVE-001 (or all SOLVE-*) | Technical feasibility and risk review (Full/Batch) |
-| SOLVE-fix-001 | planner | fix | AUDIT-001 | Revised solution addressing reviewer feedback |
-| AUDIT-002 | reviewer | re-review | SOLVE-fix-001 | Re-review of revised solution |
-| MARSHAL-001 | integrator | integrate | AUDIT-001 (or last SOLVE-* in quick) | Conflict detection and queue orchestration |
-| BUILD-001 | implementer | implement | MARSHAL-001 | Code implementation and result submission |
-| BUILD-002..M | implementer | implement | MARSHAL-001 | Parallel implementation (Batch, deferred creation) |
-
-## Mode Auto-Detection
-
-| Condition | Mode |
-|-----------|------|
-| User specifies `--mode=<M>` | Use specified mode |
-| Issue count <= 2 AND no high-priority (priority < 4) | `quick` |
-| Issue count <= 2 AND has high-priority (priority >= 4) | `full` |
-| 3-4 issues | `full` |
-| Issue count >= 5 | `batch` |
-
-## Checkpoints
-
-| Trigger | Location | Behavior |
-|---------|----------|----------|
-| Review gate | After AUDIT-* | approved/concerns → MARSHAL; rejected → SOLVE-fix (max 2 rounds) |
-| Review loop limit | fix_cycles >= 2 | Force proceed to MARSHAL with warnings |
-| Deferred BUILD creation | After MARSHAL-* (batch) | Read execution-queue.json, create BUILD tasks |
-| Pipeline stall | No ready + no running | Check missing tasks, report to user |
-
-## Completion Conditions
-
-| Mode | Completion Condition |
-|------|---------------------|
-| quick | All 4 tasks completed |
-| full | All 5 tasks (+ any fix cycle tasks) completed |
-| batch | All N EXPLORE + N SOLVE + 1 AUDIT + 1 MARSHAL + M BUILD (+ any fix cycle tasks) completed |
-
-## Parallel Spawn Rules
-
-| Pipeline | Stage | Max Parallel |
-|----------|-------|-------------|
-| Batch | EXPLORE-001..N | min(N, 5) |
-| Batch | BUILD-001..M | min(M, 3) |
-| All | All other stages | 1 |
-
-## Shared State (meta.json)
-
-| Role | State Key |
-|------|-----------| 
-| explorer | `explorer` (issue_id, complexity, impact_scope, file_count) |
-| planner | `planner` (issue_id, solution_id, task_count, is_revision) |
-| reviewer | `reviewer` (overall_verdict, review_count, scores) |
-| integrator | `integrator` (queue_size, parallel_groups, conflict_count) |
-| implementer | `implementer` (issue_id, executor, test_status, review_status) |
-
-## Message Types
-
-| Role | Types |
-|------|-------|
-| coordinator | `pipeline_selected`, `review_result`, `fix_required`, `task_unblocked`, `error`, `shutdown` |
-| explorer | `context_ready`, `error` |
-| planner | `solution_ready`, `multi_solution`, `error` |
-| reviewer | `approved`, `concerns`, `rejected`, `error` |
-| integrator | `queue_ready`, `conflict_found`, `error` |
-| implementer | `impl_complete`, `impl_failed`, `error` |
-
-## Review-Fix Cycle
-
-```
-AUDIT verdict: rejected
-    │
-    ├─ fix_cycles < 2 → create SOLVE-fix-<N> + AUDIT-<N+1> → spawn planner → wait
-    │                       ↑
-    │                   (repeat if rejected again)
-    │
-    └─ fix_cycles >= 2 → force proceed to MARSHAL with rejection warning logged
-```
-
-## Deferred BUILD Creation (Batch Mode)
-
-BUILD tasks are not created during initial dispatch. After MARSHAL-001 completes:
-1. Read `.workflow/issues/queue/execution-queue.json`
-2. Parse `parallel_groups` to determine M
-3. Create BUILD-001..M tasks with `addBlockedBy: ["MARSHAL-001"]`
-4. Assign owners: M <= 2 → "implementer"; M > 2 → "implementer-1".."implementer-M" (max 3)
-5. Spawn implementer workers via handleSpawnNext
+# Pipeline Definitions — team-issue
+
+## Available Pipelines
+
+### Quick Pipeline (4 beats, strictly serial)
+
+```
+EXPLORE-001 → SOLVE-001 → MARSHAL-001 → BUILD-001
+[explorer]    [planner]   [integrator]  [implementer]
+```
+
+Use when: 1-2 simple issues, no high-priority (priority < 4).
+
+### Full Pipeline (5 beats, with review gate)
+
+```
+EXPLORE-001 → SOLVE-001 → AUDIT-001 ─┬─(approved/concerns)→ MARSHAL-001 → BUILD-001
+[explorer]    [planner]   [reviewer]  │
+                                      └─(rejected, round<2)→ SOLVE-fix-001 → AUDIT-002 → MARSHAL-001 → BUILD-001
+```
+
+Use when: 1-4 issues with high-priority, or 3-4 issues regardless of priority.
+
+### Batch Pipeline (parallel windows)
+
+```
+[EXPLORE-001..N](parallel, max 5) → [SOLVE-001..N](sequential) → AUDIT-001 → MARSHAL-001 → [BUILD-001..M](parallel, max 3, deferred)
+```
+
+Use when: 5+ issues.
+
+Note: BUILD tasks are created dynamically after MARSHAL completes and execution-queue.json is available.
+
+## Task Metadata Registry
+
+| Task ID | Role | Phase | Dependencies | Description |
+|---------|------|-------|-------------|-------------|
+| EXPLORE-001 | explorer | explore | (none) | Context analysis and impact assessment |
+| EXPLORE-002..N | explorer | explore | (none) | Parallel exploration (Batch mode only, max 5) |
+| SOLVE-001 | planner | plan | EXPLORE-001 (or all EXPLORE-*) | Solution design and task decomposition |
+| SOLVE-002..N | planner | plan | all EXPLORE-* | Parallel solution design (Batch mode only) |
+| AUDIT-001 | reviewer | review | SOLVE-001 (or all SOLVE-*) | Technical feasibility and risk review (Full/Batch) |
+| SOLVE-fix-001 | planner | fix | AUDIT-001 | Revised solution addressing reviewer feedback |
+| AUDIT-002 | reviewer | re-review | SOLVE-fix-001 | Re-review of revised solution |
+| MARSHAL-001 | integrator | integrate | AUDIT-001 (or last SOLVE-* in quick) | Conflict detection and queue orchestration |
+| BUILD-001 | implementer | implement | MARSHAL-001 | Code implementation and result submission |
+| BUILD-002..M | implementer | implement | MARSHAL-001 | Parallel implementation (Batch, deferred creation) |
+
+## Mode Auto-Detection
+
+| Condition | Mode |
+|-----------|------|
+| User specifies `--mode=<M>` | Use specified mode |
+| Issue count <= 2 AND no high-priority (priority < 4) | `quick` |
+| Issue count <= 2 AND has high-priority (priority >= 4) | `full` |
+| 3-4 issues | `full` |
+| Issue count >= 5 | `batch` |
+
+## Checkpoints
+
+| Trigger | Location | Behavior |
+|---------|----------|----------|
+| Review gate | After AUDIT-* | approved/concerns → MARSHAL; rejected → SOLVE-fix (max 2 rounds) |
+| Review loop limit | fix_cycles >= 2 | Force proceed to MARSHAL with warnings |
+| Deferred BUILD creation | After MARSHAL-* (batch) | Read execution-queue.json, create BUILD tasks |
+| Pipeline stall | No ready + no running | Check missing tasks, report to user |
+
+## Completion Conditions
+
+| Mode | Completion Condition |
+|------|---------------------|
+| quick | All 4 tasks completed |
+| full | All 5 tasks (+ any fix cycle tasks) completed |
+| batch | All N EXPLORE + N SOLVE + 1 AUDIT + 1 MARSHAL + M BUILD (+ any fix cycle tasks) completed |
+
+## Parallel Spawn Rules
+
+| Pipeline | Stage | Max Parallel |
+|----------|-------|-------------|
+| Batch | EXPLORE-001..N | min(N, 5) |
+| Batch | BUILD-001..M | min(M, 3) |
+| All | All other stages | 1 |
+
+## Shared State (meta.json)
+
+| Role | State Key |
+|------|-----------| 
+| explorer | `explorer` (issue_id, complexity, impact_scope, file_count) |
+| planner | `planner` (issue_id, solution_id, task_count, is_revision) |
+| reviewer | `reviewer` (overall_verdict, review_count, scores) |
+| integrator | `integrator` (queue_size, parallel_groups, conflict_count) |
+| implementer | `implementer` (issue_id, executor, test_status, review_status) |
+
+## Message Types
+
+| Role | Types |
+|------|-------|
+| coordinator | `pipeline_selected`, `review_result`, `fix_required`, `task_unblocked`, `error`, `shutdown` |
+| explorer | `context_ready`, `error` |
+| planner | `solution_ready`, `multi_solution`, `error` |
+| reviewer | `approved`, `concerns`, `rejected`, `error` |
+| integrator | `queue_ready`, `conflict_found`, `error` |
+| implementer | `impl_complete`, `impl_failed`, `error` |
+
+## Review-Fix Cycle
+
+```
+AUDIT verdict: rejected
+    │
+    ├─ fix_cycles < 2 → create SOLVE-fix-<N> + AUDIT-<N+1> → spawn planner → wait
+    │                       ↑
+    │                   (repeat if rejected again)
+    │
+    └─ fix_cycles >= 2 → force proceed to MARSHAL with rejection warning logged
+```
+
+## Deferred BUILD Creation (Batch Mode)
+
+BUILD tasks are not created during initial dispatch. After MARSHAL-001 completes:
+1. Read `.workflow/issues/queue/execution-queue.json`
+2. Parse `parallel_groups` to determine M
+3. Create BUILD-001..M tasks with `addBlockedBy: ["MARSHAL-001"]`
+4. Assign owners: M <= 2 → "implementer"; M > 2 → "implementer-1".."implementer-M" (max 3)
+5. Spawn implementer workers via handleSpawnNext

package/.codex/skills/team-lifecycle-v4/MIGRATION-PLAN.md

@@ -19,7 +19,7 @@
 | Worker spawn | `Agent({ subagent_type: "team-worker", prompt })` | `spawn_agent({ agent_type: "tlv4_worker", items })` |
 | Supervisor spawn | `Agent({ subagent_type: "team-supervisor", prompt })` | `spawn_agent({ agent_type: "tlv4_supervisor", items })` |
 | Supervisor wake | `SendMessage({ recipient: "supervisor", content })` | `send_input({ id: supervisorId, items })` |
-| Supervisor shutdown | `SendMessage({ type: "shutdown_request" })` | `close_agent({ id: supervisorId })` |
+| Supervisor shutdown | `SendMessage({ type: "shutdown_request" })` | `close_agent({ target: supervisorId })` |
 | 等待完成 | 后台回调 -> monitor.md | `wait_agent({ ids, timeout_ms })` |
 | 任务状态 | `TaskCreate` / `TaskUpdate` | `tasks.json` 文件读写 |
 | 团队管理 | `TeamCreate` / `TeamDelete` | session folder init / cleanup |
@@ -222,14 +222,14 @@ scope: [${task.deps}]
 pipeline_progress: ${done}/${total} tasks completed` }
   ]
 })
-wait_agent({ ids: [supervisorId], timeout_ms: 300000 })
+wait_agent({ targets: [supervisorId], timeout_ms: 300000 })
 ```
 
 ### Supervisor Shutdown
 
 ```javascript
 // 对齐 Claude Code SendMessage({ type: "shutdown_request" })
-close_agent({ id: supervisorId })
+close_agent({ target: supervisorId })
 ```
 
 ### Wave 执行引擎
@@ -300,7 +300,7 @@ pipeline_phase: ${task.pipeline_phase}` },
 
   // 2) 批量等待
   if (agentMap.length > 0) {
-    wait_agent({ ids: agentMap.map(a => a.agentId), timeout_ms: 900000 })
+    wait_agent({ targets: agentMap.map(a => a.agentId), timeout_ms: 900000 })
   }
 
   // 3) 收集结果，合并到 tasks.json
@@ -315,7 +315,7 @@ pipeline_phase: ${task.pipeline_phase}` },
       state.tasks[taskId].status = 'failed'
       state.tasks[taskId].error = 'No discovery file produced'
     }
-    close_agent({ id: agentId })
+    close_agent({ target: agentId })
   }
 
   // 4) 执行 CHECKPOINT 任务 (send_input 唤醒 supervisor)
@@ -329,7 +329,7 @@ scope: [${task.deps.join(', ')}]
 pipeline_progress: ${completedCount}/${totalCount} tasks completed` }
       ]
     })
-    wait_agent({ ids: [supervisorId], timeout_ms: 300000 })
+    wait_agent({ targets: [supervisorId], timeout_ms: 300000 })
 
     // 读取 checkpoint 报告
     try {