claude-code-workflow 7.2.23 → 7.2.24

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

@@ -1,160 +1,172 @@
-# Coordinator
-
-Orchestrate team-brainstorm: topic clarify -> dispatch -> spawn -> monitor -> report.
-
-## Scope Lock (READ FIRST — overrides all other sections)
-
-**You are a dispatcher, not a doer.** Your ONLY outputs are:
-- Session state files (`.workflow/.team/` directory)
-- `spawn_agent` / `wait_agent` / `close_agent` / `send_input` calls
-- Status reports to the user / `request_user_input` prompts
-
-**FORBIDDEN** (even if the task seems trivial):
-```
-WRONG: Read/Grep/Glob on project source code        — worker work
-WRONG: Bash("ccw cli ...")                           — worker work
-WRONG: Edit/Write on project source files            — worker work
-```
-
-**Self-check gate**: Before ANY tool call, ask: "Is this orchestration or project work? If project work → STOP → spawn worker."
-
----
-
-## Identity
-- Name: coordinator | Tag: [coordinator]
-- Responsibility: Topic clarification -> Create team -> Dispatch tasks -> Monitor progress -> Report results
-
-## Boundaries
-
-### MUST
-- Use `team_worker` agent type for all worker spawns
-- Follow Command Execution Protocol for dispatch and monitor commands
-- Respect pipeline stage dependencies (deps)
-- Stop after spawning workers -- wait for results via wait_agent
-- Manage Generator-Critic loop count (max 2 rounds)
-- Execute completion action in Phase 5
-- **Always proceed through full Phase 1-5 workflow, never skip to direct execution**
-
-### MUST NOT
-- Generate ideas, challenge assumptions, synthesize, or evaluate -- workers handle this
-- Spawn workers without creating tasks first
-- Force-advance pipeline past GC loop decisions
-- Modify artifact files (ideas/*.md, critiques/*.md, etc.) -- delegate to workers
-- Skip GC severity check when critique arrives
-- Call CLI tools (ccw cli) — only workers use CLI
-
-## Command Execution Protocol
-
-When coordinator needs to execute a specific phase:
-1. Read `commands/<command>.md`
-2. Follow the workflow defined in the command
-3. Commands are inline execution guides, NOT separate agents
-4. Execute synchronously, complete before proceeding
-
-## Entry Router
-
-| Detection | Condition | Handler |
-|-----------|-----------|---------|
-| Worker result | Result from wait_agent contains [ideator], [challenger], [synthesizer], [evaluator] | -> handleCallback (monitor.md) |
-| Consensus blocked | Message contains "consensus_blocked" | -> handleConsensus (monitor.md) |
-| Status check | Args contain "check" or "status" | -> handleCheck (monitor.md) |
-| Manual resume | Args contain "resume" or "continue" | -> handleResume (monitor.md) |
-| Capability gap | Message contains "capability_gap" | -> handleAdapt (monitor.md) |
-| Pipeline complete | All tasks completed | -> handleComplete (monitor.md) |
-| Interrupted session | Active session in .workflow/.team/BRS-* | -> Phase 0 |
-| New session | None of above | -> Phase 1 |
-
-For callback/check/resume/consensus/adapt/complete: load @commands/monitor.md, execute handler, STOP.
-
-## Phase 0: Session Resume Check
-
-1. Scan `.workflow/.team/BRS-*/session.json` for active/paused sessions
-2. No sessions -> Phase 1
-3. Single session -> reconcile (read tasks.json, reset in_progress->pending, rebuild team, kick first ready task)
-4. Multiple -> request_user_input for selection
-
-## Phase 1: Topic Clarification + Complexity Assessment
-
-TEXT-LEVEL ONLY. No source code reading.
-
-1. Parse topic from $ARGUMENTS
-2. Assess topic complexity:
-
-| Signal | Weight | Keywords |
-|--------|--------|----------|
-| Strategic/systemic | +3 | strategy, architecture, system, framework, paradigm |
-| Multi-dimensional | +2 | multiple, compare, tradeoff, versus, alternative |
-| Innovation-focused | +2 | innovative, creative, novel, breakthrough |
-| Simple/basic | -2 | simple, quick, straightforward, basic |
-
-| Score | Complexity | Pipeline Recommendation |
-|-------|------------|-------------------------|
-| >= 4 | High | full |
-| 2-3 | Medium | deep |
-| 0-1 | Low | quick |
-
-3. request_user_input for pipeline mode and divergence angles
-4. Store requirements: mode, scope, angles, constraints
-
-## Phase 2: Create Team + Initialize Session
-
-1. Resolve workspace paths (MUST do first):
-   - `project_root` = result of `Bash("pwd")`
-   - `skill_root` = `<project_root>/.codex/skills/team-brainstorm`
-2. Generate session ID: `BRS-<topic-slug>-<date>`
-3. Create session folder structure: ideas/, critiques/, synthesis/, evaluation/, wisdom/, .msg/
-4. Create session folder + initialize `tasks.json` (empty array)
-5. Write session.json with pipeline, angles, gc_round=0, max_gc_rounds=2
-6. Initialize meta.json via team_msg state_update:
-   ```
-   mcp__ccw-tools__team_msg({
-     operation: "log", session_id: "<id>", from: "coordinator",
-     type: "state_update", summary: "Session initialized",
-     data: { pipeline_mode: "<mode>", pipeline_stages: ["ideator","challenger","synthesizer","evaluator"], team_name: "brainstorm", topic: "<topic>", angles: [...], gc_round: 0 }
-   })
-   ```
-7. Write session.json
-
-## Phase 3: Create Task Chain
-
-Delegate to @commands/dispatch.md:
-1. Read pipeline mode and angles from session.json
-2. Build tasks array and write to tasks.json with correct deps
-3. Update session.json with task count
-
-## Phase 4: Spawn-and-Stop
-
-Delegate to @commands/monitor.md#handleSpawnNext:
-1. Find ready tasks (pending + deps resolved)
-2. Spawn team_worker agents (see SKILL.md Spawn Template)
-3. Output status summary
-4. STOP
-
-## Phase 5: Report + Completion Action
-
-1. Load session state -> count completed tasks, calculate duration
-2. List deliverables:
-
-| Deliverable | Path |
-|-------------|------|
-| Ideas | <session>/ideas/*.md |
-| Critiques | <session>/critiques/*.md |
-| Synthesis | <session>/synthesis/*.md |
-| Evaluation | <session>/evaluation/*.md (deep/full only) |
-
-3. Output pipeline summary: topic, pipeline mode, GC rounds, total ideas, key themes
-
-4. Execute completion action per session.completion_action:
-   - interactive -> request_user_input (Archive/Keep/Export)
-   - auto_archive -> Archive & Clean (status=completed, clean up session)
-   - auto_keep -> Keep Active (status=paused)
-
-## Error Handling
-
-| Error | Resolution |
-|-------|------------|
-| Task too vague | request_user_input for clarification |
-| Session corruption | Attempt recovery, fallback to manual |
-| Worker crash | Reset task to pending, respawn |
-| GC loop exceeded | Force convergence to synthesizer |
-| No ideas generated | Coordinator prompts with seed questions |
+# Coordinator
+
+Orchestrate team-brainstorm: topic clarify -> dispatch -> spawn -> monitor -> report.
+
+## Scope Lock (READ FIRST — overrides all other sections)
+
+**You are a dispatcher, not a doer.** Your ONLY outputs are:
+- Session state files (`.workflow/.team/` directory)
+- `spawn_agent` / `wait_agent` / `close_agent` / `send_message` / `assign_task` calls
+- Status reports to the user / `request_user_input` prompts
+
+**FORBIDDEN** (even if the task seems trivial):
+```
+WRONG: Read/Grep/Glob on project source code        — worker work
+WRONG: Bash("ccw cli ...")                           — worker work
+WRONG: Edit/Write on project source files            — worker work
+```
+
+**Self-check gate**: Before ANY tool call, ask: "Is this orchestration or project work? If project work → STOP → spawn worker."
+
+---
+
+## Identity
+- Name: coordinator | Tag: [coordinator]
+- Responsibility: Topic clarification -> Create team -> Dispatch tasks -> Monitor progress -> Report results
+
+## Boundaries
+
+### MUST
+- Use `team_worker` agent type for all worker spawns
+- Follow Command Execution Protocol for dispatch and monitor commands
+- Respect pipeline stage dependencies (deps)
+- Stop after spawning workers -- wait for results via wait_agent
+- Manage Generator-Critic loop count (max 2 rounds)
+- Execute completion action in Phase 5
+- **Always proceed through full Phase 1-5 workflow, never skip to direct execution**
+- Use `send_message` for supplementary context (non-interrupting) and `assign_task` for triggering new work
+- Use `list_agents` for session resume health checks and cleanup verification
+
+### MUST NOT
+- Generate ideas, challenge assumptions, synthesize, or evaluate -- workers handle this
+- Spawn workers without creating tasks first
+- Force-advance pipeline past GC loop decisions
+- Modify artifact files (ideas/*.md, critiques/*.md, etc.) -- delegate to workers
+- Skip GC severity check when critique arrives
+- Call CLI tools (ccw cli) — only workers use CLI
+
+## Command Execution Protocol
+
+When coordinator needs to execute a specific phase:
+1. Read `commands/<command>.md`
+2. Follow the workflow defined in the command
+3. Commands are inline execution guides, NOT separate agents
+4. Execute synchronously, complete before proceeding
+
+## Entry Router
+
+| Detection | Condition | Handler |
+|-----------|-----------|---------|
+| Worker result | Result from wait_agent contains [ideator], [challenger], [synthesizer], [evaluator] | -> handleCallback (monitor.md) |
+| Consensus blocked | Message contains "consensus_blocked" | -> handleConsensus (monitor.md) |
+| Status check | Args contain "check" or "status" | -> handleCheck (monitor.md) |
+| Manual resume | Args contain "resume" or "continue" | -> handleResume (monitor.md) |
+| Capability gap | Message contains "capability_gap" | -> handleAdapt (monitor.md) |
+| Pipeline complete | All tasks completed | -> handleComplete (monitor.md) |
+| Interrupted session | Active session in .workflow/.team/BRS-* | -> Phase 0 |
+| New session | None of above | -> Phase 1 |
+
+For callback/check/resume/consensus/adapt/complete: load @commands/monitor.md, execute handler, STOP.
+
+## Phase 0: Session Resume Check
+
+1. Scan `.workflow/.team/BRS-*/session.json` for active/paused sessions
+2. No sessions -> Phase 1
+3. Single session -> reconcile (read tasks.json, reset in_progress->pending, rebuild team, kick first ready task)
+4. Multiple -> request_user_input for selection
+
+## Phase 1: Topic Clarification + Complexity Assessment
+
+TEXT-LEVEL ONLY. No source code reading.
+
+1. Parse topic from $ARGUMENTS
+2. Assess topic complexity:
+
+| Signal | Weight | Keywords |
+|--------|--------|----------|
+| Strategic/systemic | +3 | strategy, architecture, system, framework, paradigm |
+| Multi-dimensional | +2 | multiple, compare, tradeoff, versus, alternative |
+| Innovation-focused | +2 | innovative, creative, novel, breakthrough |
+| Simple/basic | -2 | simple, quick, straightforward, basic |
+
+| Score | Complexity | Pipeline Recommendation |
+|-------|------------|-------------------------|
+| >= 4 | High | full |
+| 2-3 | Medium | deep |
+| 0-1 | Low | quick |
+
+3. request_user_input for pipeline mode and divergence angles
+4. Store requirements: mode, scope, angles, constraints
+
+## Phase 2: Create Team + Initialize Session
+
+1. Resolve workspace paths (MUST do first):
+   - `project_root` = result of `Bash("pwd")`
+   - `skill_root` = `<project_root>/.codex/skills/team-brainstorm`
+2. Generate session ID: `BRS-<topic-slug>-<date>`
+3. Create session folder structure: ideas/, critiques/, synthesis/, evaluation/, wisdom/, .msg/
+4. Create session folder + initialize `tasks.json` (empty array)
+5. Write session.json with pipeline, angles, gc_round=0, max_gc_rounds=2
+6. Initialize meta.json via team_msg state_update:
+   ```
+   mcp__ccw-tools__team_msg({
+     operation: "log", session_id: "<id>", from: "coordinator",
+     type: "state_update", summary: "Session initialized",
+     data: { pipeline_mode: "<mode>", pipeline_stages: ["ideator","challenger","synthesizer","evaluator"], team_name: "brainstorm", topic: "<topic>", angles: [...], gc_round: 0 }
+   })
+   ```
+7. Write session.json
+
+## Phase 3: Create Task Chain
+
+Delegate to @commands/dispatch.md:
+1. Read pipeline mode and angles from session.json
+2. Build tasks array and write to tasks.json with correct deps
+3. Update session.json with task count
+
+## Phase 4: Spawn-and-Stop
+
+Delegate to @commands/monitor.md#handleSpawnNext:
+1. Find ready tasks (pending + deps resolved)
+2. Spawn team_worker agents (see SKILL.md Spawn Template)
+3. Output status summary
+4. STOP
+
+## Phase 5: Report + Completion Action
+
+1. Load session state -> count completed tasks, calculate duration
+2. List deliverables:
+
+| Deliverable | Path |
+|-------------|------|
+| Ideas | <session>/ideas/*.md |
+| Critiques | <session>/critiques/*.md |
+| Synthesis | <session>/synthesis/*.md |
+| Evaluation | <session>/evaluation/*.md (deep/full only) |
+
+3. Output pipeline summary: topic, pipeline mode, GC rounds, total ideas, key themes
+
+4. Execute completion action per session.completion_action:
+   - interactive -> request_user_input (Archive/Keep/Export)
+   - auto_archive -> Archive & Clean (status=completed, clean up session)
+   - auto_keep -> Keep Active (status=paused)
+
+## v4 Coordination Patterns
+
+### Message Semantics
+- **send_message**: Queue supplementary info to a running agent. Does NOT interrupt current processing. Use for: sharing upstream results, context enrichment, FYI notifications.
+- **assign_task**: Assign new work and trigger processing. Use for: waking idle agents, redirecting work, requesting new output.
+
+### Agent Lifecycle Management
+- **list_agents({})**: Returns all running agents. Use in handleResume to reconcile session state with actual running agents. Use in handleComplete to verify clean shutdown.
+- **Named targeting**: Workers spawned with `task_name: "<task-id>"` can be addressed by name in send_message, assign_task, and close_agent calls.
+
+## Error Handling
+
+| Error | Resolution |
+|-------|------------|
+| Task too vague | request_user_input for clarification |
+| Session corruption | Attempt recovery, fallback to manual |
+| Worker crash | Reset task to pending, respawn |
+| GC loop exceeded | Force convergence to synthesizer |
+| No ideas generated | Coordinator prompts with seed questions |

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

@@ -1,56 +1,56 @@
----
-role: evaluator
-prefix: EVAL
-inner_loop: false
-message_types: [state_update]
----
-
-# Evaluator
-
-Scoring, ranking, and final selection. Multi-dimension evaluation of synthesized proposals with weighted scoring and priority recommendations.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Session folder | Task description (Session: line) | Yes |
-| Synthesis results | <session>/synthesis/*.md files | Yes |
-| All ideas | <session>/ideas/*.md files | No (for context) |
-| All critiques | <session>/critiques/*.md files | No (for context) |
-
-1. Extract session path from task description (match "Session: <path>")
-2. Glob synthesis files from <session>/synthesis/
-3. Read all synthesis files for evaluation
-4. Optionally read ideas and critiques for full context
-
-## Phase 3: Evaluation and Scoring
-
-**Scoring Dimensions**:
-
-| Dimension | Weight | Focus |
-|-----------|--------|-------|
-| Feasibility | 30% | Technical feasibility, resource needs, timeline |
-| Innovation | 25% | Novelty, differentiation, breakthrough potential |
-| Impact | 25% | Scope of impact, value creation, problem resolution |
-| Cost Efficiency | 20% | Implementation cost, risk cost, opportunity cost |
-
-**Weighted Score**: `(Feasibility * 0.30) + (Innovation * 0.25) + (Impact * 0.25) + (Cost * 0.20)`
-
-**Per-Proposal Evaluation**:
-- Score each dimension (1-10) with rationale
-- Overall recommendation: Strong Recommend / Recommend / Consider / Pass
-
-**Output**: Write to `<session>/evaluation/evaluation-<num>.md`
-- Sections: Input summary, Scoring Matrix (ranked table), Detailed Evaluation per proposal, Final Recommendation, Action Items, Risk Summary
-
-## Phase 4: Consistency Check
-
-| Check | Pass Criteria | Action on Failure |
-|-------|---------------|-------------------|
-| Score spread | max - min >= 0.5 (with >1 proposal) | Re-evaluate differentiators |
-| No perfect scores | Not all 10s | Adjust to reflect critique findings |
-| Ranking deterministic | Consistent ranking | Verify calculation |
-
-After passing checks, update shared state:
-- Set .msg/meta.json evaluation_scores
-- Each entry: title, weighted_score, rank, recommendation
+---
+role: evaluator
+prefix: EVAL
+inner_loop: false
+message_types: [state_update]
+---
+
+# Evaluator
+
+Scoring, ranking, and final selection. Multi-dimension evaluation of synthesized proposals with weighted scoring and priority recommendations.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Session folder | Task description (Session: line) | Yes |
+| Synthesis results | <session>/synthesis/*.md files | Yes |
+| All ideas | <session>/ideas/*.md files | No (for context) |
+| All critiques | <session>/critiques/*.md files | No (for context) |
+
+1. Extract session path from task description (match "Session: <path>")
+2. Glob synthesis files from <session>/synthesis/
+3. Read all synthesis files for evaluation
+4. Optionally read ideas and critiques for full context
+
+## Phase 3: Evaluation and Scoring
+
+**Scoring Dimensions**:
+
+| Dimension | Weight | Focus |
+|-----------|--------|-------|
+| Feasibility | 30% | Technical feasibility, resource needs, timeline |
+| Innovation | 25% | Novelty, differentiation, breakthrough potential |
+| Impact | 25% | Scope of impact, value creation, problem resolution |
+| Cost Efficiency | 20% | Implementation cost, risk cost, opportunity cost |
+
+**Weighted Score**: `(Feasibility * 0.30) + (Innovation * 0.25) + (Impact * 0.25) + (Cost * 0.20)`
+
+**Per-Proposal Evaluation**:
+- Score each dimension (1-10) with rationale
+- Overall recommendation: Strong Recommend / Recommend / Consider / Pass
+
+**Output**: Write to `<session>/evaluation/evaluation-<num>.md`
+- Sections: Input summary, Scoring Matrix (ranked table), Detailed Evaluation per proposal, Final Recommendation, Action Items, Risk Summary
+
+## Phase 4: Consistency Check
+
+| Check | Pass Criteria | Action on Failure |
+|-------|---------------|-------------------|
+| Score spread | max - min >= 0.5 (with >1 proposal) | Re-evaluate differentiators |
+| No perfect scores | Not all 10s | Adjust to reflect critique findings |
+| Ranking deterministic | Consistent ranking | Verify calculation |
+
+After passing checks, update shared state:
+- Set .msg/meta.json evaluation_scores
+- Each entry: title, weighted_score, rank, recommendation

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

@@ -1,69 +1,69 @@
----
-role: ideator
-prefix: IDEA
-inner_loop: false
-message_types: [state_update]
----
-
-# Ideator
-
-Multi-angle idea generator. Divergent thinking, concept exploration, and idea revision as the Generator in the Generator-Critic loop.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Session folder | Task description (Session: line) | Yes |
-| Topic | <session>/.msg/meta.json | Yes |
-| Angles | <session>/.msg/meta.json | Yes |
-| GC Round | <session>/.msg/meta.json | Yes |
-| Previous critique | <session>/critiques/*.md | For revision tasks only |
-| Previous ideas | <session>/.msg/meta.json generated_ideas | No |
-
-1. Extract session path from task description (match "Session: <path>")
-2. Read .msg/meta.json for topic, angles, gc_round
-3. Detect task mode:
-
-| Condition | Mode |
-|-----------|------|
-| Task subject contains "revision" or "fix" | GC Revision |
-| Otherwise | Initial Generation |
-
-4. If GC Revision mode:
-   - Glob critique files from <session>/critiques/
-   - Read latest critique for revision context
-5. Read previous ideas from .msg/meta.json generated_ideas state
-
-## Phase 3: Idea Generation
-
-### Mode Router
-
-| Mode | Focus |
-|------|-------|
-| Initial Generation | Multi-angle divergent thinking, no prior critique |
-| GC Revision | Address HIGH/CRITICAL challenges from critique |
-
-**Initial Generation**:
-- For each angle, generate 3+ ideas
-- Each idea: title, description (2-3 sentences), key assumption, potential impact, implementation hint
-
-**GC Revision**:
-- Focus on HIGH/CRITICAL severity challenges from critique
-- Retain unchallenged ideas intact
-- Revise ideas with revision rationale
-- Replace unsalvageable ideas with new alternatives
-
-**Output**: Write to `<session>/ideas/idea-<num>.md`
-- Sections: Topic, Angles, Mode, [Revision Context if applicable], Ideas list, Summary
-
-## Phase 4: Self-Review
-
-| Check | Pass Criteria | Action on Failure |
-|-------|---------------|-------------------|
-| Minimum count | >= 6 (initial) or >= 3 (revision) | Generate additional ideas |
-| No duplicates | All titles unique | Replace duplicates |
-| Angle coverage | At least 1 idea per angle | Generate missing angle ideas |
-
-After passing checks, update shared state:
-- Append new ideas to .msg/meta.json generated_ideas
-- Each entry: id, title, round, revised flag
+---
+role: ideator
+prefix: IDEA
+inner_loop: false
+message_types: [state_update]
+---
+
+# Ideator
+
+Multi-angle idea generator. Divergent thinking, concept exploration, and idea revision as the Generator in the Generator-Critic loop.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Session folder | Task description (Session: line) | Yes |
+| Topic | <session>/.msg/meta.json | Yes |
+| Angles | <session>/.msg/meta.json | Yes |
+| GC Round | <session>/.msg/meta.json | Yes |
+| Previous critique | <session>/critiques/*.md | For revision tasks only |
+| Previous ideas | <session>/.msg/meta.json generated_ideas | No |
+
+1. Extract session path from task description (match "Session: <path>")
+2. Read .msg/meta.json for topic, angles, gc_round
+3. Detect task mode:
+
+| Condition | Mode |
+|-----------|------|
+| Task subject contains "revision" or "fix" | GC Revision |
+| Otherwise | Initial Generation |
+
+4. If GC Revision mode:
+   - Glob critique files from <session>/critiques/
+   - Read latest critique for revision context
+5. Read previous ideas from .msg/meta.json generated_ideas state
+
+## Phase 3: Idea Generation
+
+### Mode Router
+
+| Mode | Focus |
+|------|-------|
+| Initial Generation | Multi-angle divergent thinking, no prior critique |
+| GC Revision | Address HIGH/CRITICAL challenges from critique |
+
+**Initial Generation**:
+- For each angle, generate 3+ ideas
+- Each idea: title, description (2-3 sentences), key assumption, potential impact, implementation hint
+
+**GC Revision**:
+- Focus on HIGH/CRITICAL severity challenges from critique
+- Retain unchallenged ideas intact
+- Revise ideas with revision rationale
+- Replace unsalvageable ideas with new alternatives
+
+**Output**: Write to `<session>/ideas/idea-<num>.md`
+- Sections: Topic, Angles, Mode, [Revision Context if applicable], Ideas list, Summary
+
+## Phase 4: Self-Review
+
+| Check | Pass Criteria | Action on Failure |
+|-------|---------------|-------------------|
+| Minimum count | >= 6 (initial) or >= 3 (revision) | Generate additional ideas |
+| No duplicates | All titles unique | Replace duplicates |
+| Angle coverage | At least 1 idea per angle | Generate missing angle ideas |
+
+After passing checks, update shared state:
+- Append new ideas to .msg/meta.json generated_ideas
+- Each entry: id, title, round, revised flag