claude-code-workflow 7.2.23 → 7.2.24

package/.codex/skills/team-brainstorm/roles/challenger/role.md

@@ -1,61 +1,61 @@
----
-role: challenger
-prefix: CHALLENGE
-inner_loop: false
-message_types: [state_update]
----
-
-# Challenger
-
-Devil's advocate role. Assumption challenging, feasibility questioning, risk identification. Acts as the Critic in the Generator-Critic loop.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Session folder | Task description (Session: line) | Yes |
-| Ideas | <session>/ideas/*.md files | Yes |
-| Previous critiques | <session>/.msg/meta.json critique_insights | No |
-
-1. Extract session path from task description (match "Session: <path>")
-2. Glob idea files from <session>/ideas/
-3. Read all idea files for analysis
-4. Read .msg/meta.json critique_insights to avoid repeating past challenges
-
-## Phase 3: Critical Analysis
-
-**Challenge Dimensions** (apply to each idea):
-
-| Dimension | Focus |
-|-----------|-------|
-| Assumption Validity | Does the core assumption hold? Counter-examples? |
-| Feasibility | Technical/resource/time feasibility? |
-| Risk Assessment | Worst case scenario? Hidden risks? |
-| Competitive Analysis | Better alternatives already exist? |
-
-**Severity Classification**:
-
-| Severity | Criteria |
-|----------|----------|
-| CRITICAL | Fundamental issue, idea may need replacement |
-| HIGH | Significant flaw, requires revision |
-| MEDIUM | Notable weakness, needs consideration |
-| LOW | Minor concern, does not invalidate the idea |
-
-**Generator-Critic Signal**:
-
-| Condition | Signal |
-|-----------|--------|
-| Any CRITICAL or HIGH severity | REVISION_NEEDED |
-| All MEDIUM or lower | CONVERGED |
-
-**Output**: Write to `<session>/critiques/critique-<num>.md`
-- Sections: Ideas Reviewed, Per-idea challenges with severity, Summary table with counts, GC Signal
-
-## Phase 4: Severity Summary
-
-1. Count challenges by severity level
-2. Determine signal: REVISION_NEEDED if critical+high > 0, else CONVERGED
-3. Update shared state:
-   - Append challenges to .msg/meta.json critique_insights
-   - Each entry: idea, severity, key_challenge, round
+---
+role: challenger
+prefix: CHALLENGE
+inner_loop: false
+message_types: [state_update]
+---
+
+# Challenger
+
+Devil's advocate role. Assumption challenging, feasibility questioning, risk identification. Acts as the Critic in the Generator-Critic loop.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Session folder | Task description (Session: line) | Yes |
+| Ideas | <session>/ideas/*.md files | Yes |
+| Previous critiques | <session>/.msg/meta.json critique_insights | No |
+
+1. Extract session path from task description (match "Session: <path>")
+2. Glob idea files from <session>/ideas/
+3. Read all idea files for analysis
+4. Read .msg/meta.json critique_insights to avoid repeating past challenges
+
+## Phase 3: Critical Analysis
+
+**Challenge Dimensions** (apply to each idea):
+
+| Dimension | Focus |
+|-----------|-------|
+| Assumption Validity | Does the core assumption hold? Counter-examples? |
+| Feasibility | Technical/resource/time feasibility? |
+| Risk Assessment | Worst case scenario? Hidden risks? |
+| Competitive Analysis | Better alternatives already exist? |
+
+**Severity Classification**:
+
+| Severity | Criteria |
+|----------|----------|
+| CRITICAL | Fundamental issue, idea may need replacement |
+| HIGH | Significant flaw, requires revision |
+| MEDIUM | Notable weakness, needs consideration |
+| LOW | Minor concern, does not invalidate the idea |
+
+**Generator-Critic Signal**:
+
+| Condition | Signal |
+|-----------|--------|
+| Any CRITICAL or HIGH severity | REVISION_NEEDED |
+| All MEDIUM or lower | CONVERGED |
+
+**Output**: Write to `<session>/critiques/critique-<num>.md`
+- Sections: Ideas Reviewed, Per-idea challenges with severity, Summary table with counts, GC Signal
+
+## Phase 4: Severity Summary
+
+1. Count challenges by severity level
+2. Determine signal: REVISION_NEEDED if critical+high > 0, else CONVERGED
+3. Update shared state:
+   - Append challenges to .msg/meta.json critique_insights
+   - Each entry: idea, severity, key_challenge, round

package/.codex/skills/team-brainstorm/roles/coordinator/commands/analyze.md

@@ -1,58 +1,58 @@
-# Analyze Task
-
-Parse user topic -> detect brainstorming capabilities -> assess complexity -> select pipeline.
-
-**CONSTRAINT**: Text-level analysis only. NO source code reading, NO codebase exploration.
-
-## Signal Detection
-
-| Keywords | Capability | Prefix |
-|----------|------------|--------|
-| generate, create, brainstorm, ideas, explore | ideator | IDEA |
-| challenge, critique, argue, devil, risk | challenger | CHALLENGE |
-| synthesize, integrate, combine, merge, themes | synthesizer | SYNTH |
-| evaluate, score, rank, prioritize, select | evaluator | EVAL |
-
-## Dependency Graph
-
-Natural ordering tiers:
-- Tier 0: ideator (divergent generation -- no dependencies)
-- Tier 1: challenger (requires ideator output)
-- Tier 2: ideator-revision (requires challenger output, GC loop)
-- Tier 3: synthesizer (requires last challenger output)
-- Tier 4: evaluator (requires synthesizer output, deep/full only)
-
-## Complexity Scoring
-
-| Factor | Points |
-|--------|--------|
-| Per capability needed | +1 |
-| Strategic/systemic topic | +3 |
-| Multi-dimensional analysis | +2 |
-| Innovation-focused request | +2 |
-| Simple/basic topic | -2 |
-
-Results: 0-1 Low (quick), 2-3 Medium (deep), 4+ High (full)
-
-## Pipeline Selection
-
-| Complexity | Pipeline | Tasks |
-|------------|----------|-------|
-| Low | quick | IDEA -> CHALLENGE -> SYNTH |
-| Medium | deep | IDEA -> CHALLENGE -> IDEA-fix -> CHALLENGE-2 -> SYNTH -> EVAL |
-| High | full | 3x IDEA (parallel) -> CHALLENGE -> IDEA-fix -> SYNTH -> EVAL |
-
-## Output
-
-Write <session>/task-analysis.json:
-```json
-{
-  "task_description": "<original>",
-  "pipeline_type": "<quick|deep|full>",
-  "capabilities": [{ "name": "<cap>", "prefix": "<PREFIX>", "keywords": ["..."] }],
-  "dependency_graph": { "<TASK-ID>": { "role": "<role>", "blockedBy": ["..."], "priority": "P0|P1|P2" } },
-  "roles": [{ "name": "<role>", "prefix": "<PREFIX>", "inner_loop": false }],
-  "complexity": { "score": 0, "level": "Low|Medium|High" },
-  "angles": ["Technical", "Product", "Innovation", "Risk"]
-}
-```
+# Analyze Task
+
+Parse user topic -> detect brainstorming capabilities -> assess complexity -> select pipeline.
+
+**CONSTRAINT**: Text-level analysis only. NO source code reading, NO codebase exploration.
+
+## Signal Detection
+
+| Keywords | Capability | Prefix |
+|----------|------------|--------|
+| generate, create, brainstorm, ideas, explore | ideator | IDEA |
+| challenge, critique, argue, devil, risk | challenger | CHALLENGE |
+| synthesize, integrate, combine, merge, themes | synthesizer | SYNTH |
+| evaluate, score, rank, prioritize, select | evaluator | EVAL |
+
+## Dependency Graph
+
+Natural ordering tiers:
+- Tier 0: ideator (divergent generation -- no dependencies)
+- Tier 1: challenger (requires ideator output)
+- Tier 2: ideator-revision (requires challenger output, GC loop)
+- Tier 3: synthesizer (requires last challenger output)
+- Tier 4: evaluator (requires synthesizer output, deep/full only)
+
+## Complexity Scoring
+
+| Factor | Points |
+|--------|--------|
+| Per capability needed | +1 |
+| Strategic/systemic topic | +3 |
+| Multi-dimensional analysis | +2 |
+| Innovation-focused request | +2 |
+| Simple/basic topic | -2 |
+
+Results: 0-1 Low (quick), 2-3 Medium (deep), 4+ High (full)
+
+## Pipeline Selection
+
+| Complexity | Pipeline | Tasks |
+|------------|----------|-------|
+| Low | quick | IDEA -> CHALLENGE -> SYNTH |
+| Medium | deep | IDEA -> CHALLENGE -> IDEA-fix -> CHALLENGE-2 -> SYNTH -> EVAL |
+| High | full | 3x IDEA (parallel) -> CHALLENGE -> IDEA-fix -> SYNTH -> EVAL |
+
+## Output
+
+Write <session>/task-analysis.json:
+```json
+{
+  "task_description": "<original>",
+  "pipeline_type": "<quick|deep|full>",
+  "capabilities": [{ "name": "<cap>", "prefix": "<PREFIX>", "keywords": ["..."] }],
+  "dependency_graph": { "<TASK-ID>": { "role": "<role>", "blockedBy": ["..."], "priority": "P0|P1|P2" } },
+  "roles": [{ "name": "<role>", "prefix": "<PREFIX>", "inner_loop": false }],
+  "complexity": { "score": 0, "level": "Low|Medium|High" },
+  "angles": ["Technical", "Product", "Innovation", "Risk"]
+}
+```

package/.codex/skills/team-brainstorm/roles/coordinator/commands/monitor.md

@@ -1,171 +1,212 @@
-# Monitor Pipeline
-
-Event-driven pipeline coordination. Beat model: coordinator wake -> process -> spawn -> STOP.
-
-## Constants
-
-- SPAWN_MODE: spawn_agent
-- ONE_STEP_PER_INVOCATION: true
-- FAST_ADVANCE_AWARE: true
-- WORKER_AGENT: team_worker
-- MAX_GC_ROUNDS: 2
-
-## Handler Router
-
-| Source | Handler |
-|--------|---------|
-| Message contains [ideator], [challenger], [synthesizer], [evaluator] | handleCallback |
-| "consensus_blocked" | handleConsensus |
-| "capability_gap" | handleAdapt |
-| "check" or "status" | handleCheck |
-| "resume" or "continue" | handleResume |
-| All tasks completed | handleComplete |
-| Default | handleSpawnNext |
-
-## handleCallback
-
-Worker completed. Process and advance.
-
-1. Parse message to identify role and task ID:
-
-| Message Pattern | Role Detection |
-|----------------|---------------|
-| `[ideator]` or task ID `IDEA-*` | ideator |
-| `[challenger]` or task ID `CHALLENGE-*` | challenger |
-| `[synthesizer]` or task ID `SYNTH-*` | synthesizer |
-| `[evaluator]` or task ID `EVAL-*` | evaluator |
-
-2. Mark task as completed: Read tasks.json, update matching entry status to "completed", write back
-3. Record completion in session state
-4. **Generator-Critic check** (when challenger completes):
-   - If completed task is CHALLENGE-* AND pipeline is deep or full:
-   - Read critique file for GC signal
-   - Read .msg/meta.json for gc_round
-
-   | GC Signal | gc_round < max | Action |
-   |-----------|----------------|--------|
-   | REVISION_NEEDED | Yes | Increment gc_round, unblock IDEA-fix task |
-   | REVISION_NEEDED | No (>= max) | Force convergence, unblock SYNTH |
-   | CONVERGED | - | Unblock SYNTH (skip remaining GC tasks) |
-
-   - Log team_msg with type "gc_loop_trigger" or "task_unblocked"
-   - If skipping GC tasks, mark them as completed (skip)
-
-5. Close completed agent: `close_agent({ id: <agentId> })`
-6. Proceed to handleSpawnNext
-
-## handleCheck
-
-Read-only status report, then STOP.
-
-```
-[coordinator] Pipeline Status (<pipeline-mode>)
-[coordinator] Progress: <done>/<total> (<pct>%)
-[coordinator] Active: <workers with elapsed time>
-[coordinator] Ready: <pending tasks with resolved deps>
-[coordinator] GC Rounds: <gc_round>/<max_gc_rounds>
-[coordinator] Commands: 'resume' to advance | 'check' to refresh
-```
-
-## handleResume
-
-1. Audit task list: Tasks stuck in "in_progress" -> reset to "pending"
-2. Proceed to handleSpawnNext
-
-## handleSpawnNext
-
-Find ready tasks, spawn workers, STOP.
-
-1. Collect: completedSubjects, inProgressSubjects, readySubjects
-2. No ready + work in progress -> report waiting, STOP
-3. No ready + nothing in progress -> handleComplete
-4. Has ready -> for each:
-   a. Update tasks.json entry status -> "in_progress"
-   b. team_msg log -> task_unblocked
-   c. Spawn team_worker:
-      ```
-      const agentId = spawn_agent({
-        agent_type: "team_worker",
-        items: [{ type: "text", text: `## Role Assignment
-      role: <role>
-      role_spec: ~  or <project>/.codex/skills/team-brainstorm/roles/<role>/role.md
-      session: <session-folder>
-      session_id: <session-id>
-      team_name: brainstorm
-      requirement: <task-description>
-      inner_loop: false
-
-      Read role_spec file to load Phase 2-4 domain instructions.
-      Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5 (report).` }]
-      })
-      ```
-   d. Collect agent results: `wait_agent({ ids: [agentId], timeout_ms: 900000 })`
-   e. Read discoveries from output files
-   f. Update tasks.json with results
-   g. Close agent: `close_agent({ id: agentId })`
-5. Parallel spawn rules:
-
-| Pipeline | Scenario | Spawn Behavior |
-|----------|----------|---------------|
-| Quick | Single sequential | One worker at a time |
-| Deep | Sequential with GC | One worker at a time |
-| Full | IDEA-001/002/003 unblocked | Spawn ALL 3 ideator workers in parallel |
-| Full | Other stages | One worker at a time |
-
-**Parallel ideator spawn** (Full pipeline):
-```
-const agentIds = []
-for (const task of readyIdeatorTasks) {
-  agentIds.push(spawn_agent({
-    agent_type: "team_worker",
-    items: [{ type: "text", text: `...role: ideator-<N>...` }]
-  }))
-}
-const results = wait_agent({ ids: agentIds, timeout_ms: 900000 })
-// Process results, close agents
-for (const id of agentIds) { close_agent({ id }) }
-```
-
-6. Update session, output summary, STOP
-
-## handleComplete
-
-Pipeline done. Generate report and completion action.
-
-Completion check by mode:
-| Mode | Completion Condition |
-|------|---------------------|
-| quick | All 3 tasks completed |
-| deep | All 6 tasks (+ any skipped GC tasks) completed |
-| full | All 7 tasks (+ any skipped GC tasks) completed |
-
-1. Verify all tasks completed via reading tasks.json
-2. If any tasks not completed, return to handleSpawnNext
-3. If all completed -> transition to coordinator Phase 5
-
-## handleConsensus
-
-Handle consensus_blocked signals.
-
-| Severity | Action |
-|----------|--------|
-| HIGH | Pause pipeline, notify user with findings summary |
-| MEDIUM | Log finding, attempt to continue |
-| LOW | Log finding, continue pipeline |
-
-## handleAdapt
-
-Capability gap reported mid-pipeline.
-
-1. Parse gap description
-2. Check if existing role covers it -> redirect
-3. Role count < 5 -> generate dynamic role-spec in <session>/role-specs/
-4. Create new task (add to tasks.json), spawn worker
-5. Role count >= 5 -> merge or pause
-
-## Fast-Advance Reconciliation
-
-On every coordinator wake:
-1. Read team_msg entries with type="fast_advance"
-2. Sync active_workers with spawned successors
-3. No duplicate spawns
+# Monitor Pipeline
+
+Event-driven pipeline coordination. Beat model: coordinator wake -> process -> spawn -> STOP.
+
+## Constants
+
+- SPAWN_MODE: spawn_agent
+- ONE_STEP_PER_INVOCATION: true
+- FAST_ADVANCE_AWARE: true
+- WORKER_AGENT: team_worker
+- MAX_GC_ROUNDS: 2
+
+## Handler Router
+
+| Source | Handler |
+|--------|---------|
+| Message contains [ideator], [challenger], [synthesizer], [evaluator] | handleCallback |
+| "consensus_blocked" | handleConsensus |
+| "capability_gap" | handleAdapt |
+| "check" or "status" | handleCheck |
+| "resume" or "continue" | handleResume |
+| All tasks completed | handleComplete |
+| Default | handleSpawnNext |
+
+## handleCallback
+
+Worker completed. Process and advance.
+
+1. Parse message to identify role and task ID:
+
+| Message Pattern | Role Detection |
+|----------------|---------------|
+| `[ideator]` or task ID `IDEA-*` | ideator |
+| `[challenger]` or task ID `CHALLENGE-*` | challenger |
+| `[synthesizer]` or task ID `SYNTH-*` | synthesizer |
+| `[evaluator]` or task ID `EVAL-*` | evaluator |
+
+2. Mark task as completed: Read tasks.json, update matching entry status to "completed", write back
+3. Record completion in session state
+4. **Generator-Critic check** (when challenger completes):
+   - If completed task is CHALLENGE-* AND pipeline is deep or full:
+   - Read critique file for GC signal
+   - Read .msg/meta.json for gc_round
+
+   | GC Signal | gc_round < max | Action |
+   |-----------|----------------|--------|
+   | REVISION_NEEDED | Yes | Increment gc_round, unblock IDEA-fix task |
+   | REVISION_NEEDED | No (>= max) | Force convergence, unblock SYNTH |
+   | CONVERGED | - | Unblock SYNTH (skip remaining GC tasks) |
+
+   - Log team_msg with type "gc_loop_trigger" or "task_unblocked"
+   - If skipping GC tasks, mark them as completed (skip)
+
+5. Close completed agent: `close_agent({ target: <agentId> })`
+6. Proceed to handleSpawnNext
+
+## handleCheck
+
+Read-only status report, then STOP.
+
+```
+[coordinator] Pipeline Status (<pipeline-mode>)
+[coordinator] Progress: <done>/<total> (<pct>%)
+[coordinator] Active: <workers with elapsed time>
+[coordinator] Ready: <pending tasks with resolved deps>
+[coordinator] GC Rounds: <gc_round>/<max_gc_rounds>
+[coordinator] Commands: 'resume' to advance | 'check' to refresh
+```
+
+## handleResume
+
+**Agent Health Check** (v4):
+```
+// Verify actual running agents match session state
+const runningAgents = list_agents({})
+// For each active_agent in tasks.json:
+//   - If agent NOT in runningAgents -> agent crashed
+//   - Reset that task to pending, remove from active_agents
+// This prevents stale agent references from blocking the pipeline
+```
+
+1. Audit task list: Tasks stuck in "in_progress" -> reset to "pending"
+2. Proceed to handleSpawnNext
+
+## handleSpawnNext
+
+Find ready tasks, spawn workers, STOP.
+
+1. Collect: completedSubjects, inProgressSubjects, readySubjects
+2. No ready + work in progress -> report waiting, STOP
+3. No ready + nothing in progress -> handleComplete
+4. Has ready -> for each:
+   a. Update tasks.json entry status -> "in_progress"
+   b. team_msg log -> task_unblocked
+   c. Spawn team_worker:
+      ```
+      const agentId = spawn_agent({
+        agent_type: "team_worker",
+        task_name: taskId,  // e.g., "IDEA-001" — enables named targeting
+        items: [{ type: "text", text: `## Role Assignment
+      role: <role>
+      role_spec: ~  or <project>/.codex/skills/team-brainstorm/roles/<role>/role.md
+      session: <session-folder>
+      session_id: <session-id>
+      team_name: brainstorm
+      requirement: <task-description>
+      inner_loop: false
+
+      Read role_spec file to load Phase 2-4 domain instructions.
+      Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5 (report).` }]
+      })
+      ```
+   d. Collect agent results: `wait_agent({ targets: [taskId], timeout_ms: 900000 })`
+   e. Read discoveries from output files
+   f. Update tasks.json with results
+   g. Close agent: `close_agent({ target: taskId })`  // Use task_name, not agentId
+5. Parallel spawn rules:
+
+| Pipeline | Scenario | Spawn Behavior |
+|----------|----------|---------------|
+| Quick | Single sequential | One worker at a time |
+| Deep | Sequential with GC | One worker at a time |
+| Full | IDEA-001/002/003 unblocked | Spawn ALL 3 ideator workers in parallel |
+| Full | Other stages | One worker at a time |
+
+**Parallel ideator spawn** (Full pipeline):
+```
+const agentIds = []
+for (const task of readyIdeatorTasks) {
+  agentIds.push(spawn_agent({
+    agent_type: "team_worker",
+    task_name: task.id,  // e.g., "IDEA-001" — enables named targeting
+    items: [{ type: "text", text: `...role: ideator-<N>...` }]
+  }))
+}
+// Use task_name for stable targeting (v4)
+const taskNames = readyIdeatorTasks.map(t => t.id)
+const results = wait_agent({ targets: taskNames, timeout_ms: 900000 })
+if (results.timed_out) {
+  for (const taskId of taskNames) { state.tasks[taskId].status = 'timed_out'; close_agent({ target: taskId }) }
+} else {
+  // Process results, close agents
+  for (const taskId of taskNames) { close_agent({ target: taskId }) }
+}
+```
+
+**Cross-Agent Supplementary Context** (v4):
+
+When spawning workers in a later pipeline phase, send upstream results as supplementary context to already-running workers:
+
+```
+// Example: Send ideation results to running challenger
+send_message({
+  target: "<running-agent-task-name>",
+  items: [{ type: "text", text: `## Supplementary Context\n${upstreamFindings}` }]
+})
+// Note: send_message queues info without interrupting the agent's current work
+```
+
+Use `send_message` (not `assign_task`) for supplementary info that enriches but doesn't redirect the agent's current task.
+
+6. Update session, output summary, STOP
+
+## handleComplete
+
+**Cleanup Verification** (v4):
+```
+// Verify all agents are properly closed
+const remaining = list_agents({})
+// If any team agents still running -> close_agent each
+// Ensures clean session shutdown
+```
+
+Pipeline done. Generate report and completion action.
+
+Completion check by mode:
+| Mode | Completion Condition |
+|------|---------------------|
+| quick | All 3 tasks completed |
+| deep | All 6 tasks (+ any skipped GC tasks) completed |
+| full | All 7 tasks (+ any skipped GC tasks) completed |
+
+1. Verify all tasks completed via reading tasks.json
+2. If any tasks not completed, return to handleSpawnNext
+3. If all completed -> transition to coordinator Phase 5
+
+## handleConsensus
+
+Handle consensus_blocked signals.
+
+| Severity | Action |
+|----------|--------|
+| HIGH | Pause pipeline, notify user with findings summary |
+| MEDIUM | Log finding, attempt to continue |
+| LOW | Log finding, continue pipeline |
+
+## handleAdapt
+
+Capability gap reported mid-pipeline.
+
+1. Parse gap description
+2. Check if existing role covers it -> redirect
+3. Role count < 5 -> generate dynamic role-spec in <session>/role-specs/
+4. Create new task (add to tasks.json), spawn worker
+5. Role count >= 5 -> merge or pause
+
+## Fast-Advance Reconciliation
+
+On every coordinator wake:
+1. Read team_msg entries with type="fast_advance"
+2. Sync active_workers with spawned successors
+3. No duplicate spawns