claude-code-workflow 7.2.14 → 7.2.15

package/.codex/skills/team-coordinate/SKILL.md

@@ -2,7 +2,7 @@
 name: team-coordinate
 description: Universal team coordination skill with dynamic role generation. Analyzes task, generates worker roles at runtime, decomposes into CSV tasks with dependency waves, dispatches parallel CSV agents per wave. Coordinator is orchestrator; all workers are CSV or interactive agents with dynamically generated instructions.
 argument-hint: "[-y|--yes] [-c|--concurrency N] [--continue] \"task description\""
-allowed-tools: spawn_agents_on_csv, spawn_agent, wait, send_input, close_agent, Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
+allowed-tools: spawn_agents_on_csv, spawn_agent, wait, send_input, close_agent, Read, Write, Edit, Bash, Glob, Grep, request_user_input
 ---
 
 ## Auto Mode
@@ -43,7 +43,7 @@ Universal team coordination: analyze task -> detect capabilities -> generate dyn
 |                                                                     |
 |  Phase 0: Pre-Wave Interactive (Requirement Clarification)          |
 |     +- Parse user task description                                  |
-|     +- Clarify ambiguous requirements (AskUserQuestion)             |
+|     +- Clarify ambiguous requirements (request_user_input)                 |
 |     +- Output: refined requirements for decomposition               |
 |                                                                     |
 |  Phase 1: Requirement -> CSV + Classification                       |
@@ -245,13 +245,13 @@ Write(`${sessionFolder}/wisdom/decisions.md`, '# Decisions\n')
 
 3. **Clarify if ambiguous** (skip if AUTO_YES):
    ```javascript
-   AskUserQuestion({
+   request_user_input({
      questions: [{
-       question: "Please confirm the task scope and deliverables:",
-       header: "Task Clarification",
-       multiSelect: false,
+       question: "Please confirm the task scope and deliverables.",
+       header: "Scope",
+       id: "task_scope",
        options: [
-         { label: "Proceed as described", description: "Task is clear enough" },
+         { label: "Proceed (Recommended)", description: "Task is clear enough" },
          { label: "Narrow scope", description: "Specify files/modules/areas" },
          { label: "Add constraints", description: "Timeline, tech stack, style" }
        ]
@@ -482,13 +482,13 @@ Session: ${sessionFolder}
 
 // 2. Completion action
 if (!AUTO_YES) {
-  const choice = AskUserQuestion({
+  const choice = request_user_input({
     questions: [{
-      question: "Team pipeline complete. What would you like to do?",
-      header: "Completion",
-      multiSelect: false,
+      question: "Team pipeline complete. Choose next action.",
+      header: "Done",
+      id: "completion",
       options: [
-        { label: "Archive & Clean (Recommended)", description: "Archive session, output final summary" },
+        { label: "Archive (Recommended)", description: "Archive session, output final summary" },
         { label: "Keep Active", description: "Keep session for follow-up work" },
         { label: "Retry Failed", description: "Re-run failed tasks" }
       ]
@@ -609,7 +609,7 @@ See `instructions/agent-instruction.md` for the base instruction template that i
 | discoveries.ndjson corrupt | Ignore malformed lines, continue with valid entries |
 | No capabilities detected | Default to single `general` role with TASK prefix |
 | All capabilities merge to one | Valid: single-role execution, reduced overhead |
-| Task description too vague | AskUserQuestion for clarification in Phase 0 |
+| Task description too vague | request_user_input for clarification in Phase 0 |
 | Continue mode: no session found | List available sessions, prompt user to select |
 | Role instruction generation fails | Fall back to generic instruction template |
 
@@ -627,41 +627,41 @@ See `instructions/agent-instruction.md` for the base instruction template that i
 8. **Dynamic Roles**: All worker roles are generated at runtime from task analysis -- no static role registry
 9. **Cleanup Temp Files**: Remove wave-{N}.csv after results are merged
 10. **DO NOT STOP**: Continuous execution until all waves complete or all remaining tasks are skipped
-
-
----
-
-## Coordinator Role Constraints (Main Agent)
-
-**CRITICAL**: The coordinator (main agent executing this skill) is responsible for **orchestration only**, NOT implementation.
-
-15. **Coordinator Does NOT Execute Code**: The main agent MUST NOT write, modify, or implement any code directly. All implementation work is delegated to spawned team agents. The coordinator only:
-    - Spawns agents with task assignments
-    - Waits for agent callbacks
-    - Merges results and coordinates workflow
-    - Manages workflow transitions between phases
-
-16. **Patient Waiting is Mandatory**: Agent execution takes significant time (typically 10-30 minutes per phase, sometimes longer). The coordinator MUST:
-    - Wait patiently for `wait()` calls to complete
-    - NOT skip workflow steps due to perceived delays
-    - NOT assume agents have failed just because they're taking time
-    - Trust the timeout mechanisms defined in the skill
-
-17. **Use send_input for Clarification**: When agents need guidance or appear stuck, the coordinator MUST:
-    - Use `send_input()` to ask questions or provide clarification
-    - NOT skip the agent or move to next phase prematurely
-    - Give agents opportunity to respond before escalating
-    - Example: `send_input({ id: agent_id, message: "Please provide status update or clarify blockers" })`
-
-18. **No Workflow Shortcuts**: The coordinator MUST NOT:
-    - Skip phases or stages defined in the workflow
-    - Bypass required approval or review steps
-    - Execute dependent tasks before prerequisites complete
-    - Assume task completion without explicit agent callback
-    - Make up or fabricate agent results
-
-19. **Respect Long-Running Processes**: This is a complex multi-agent workflow that requires patience:
-    - Total execution time may range from 30-90 minutes or longer
-    - Each phase may take 10-30 minutes depending on complexity
-    - The coordinator must remain active and attentive throughout the entire process
-    - Do not terminate or skip steps due to time concerns
+
+
+---
+
+## Coordinator Role Constraints (Main Agent)
+
+**CRITICAL**: The coordinator (main agent executing this skill) is responsible for **orchestration only**, NOT implementation.
+
+15. **Coordinator Does NOT Execute Code**: The main agent MUST NOT write, modify, or implement any code directly. All implementation work is delegated to spawned team agents. The coordinator only:
+    - Spawns agents with task assignments
+    - Waits for agent callbacks
+    - Merges results and coordinates workflow
+    - Manages workflow transitions between phases
+
+16. **Patient Waiting is Mandatory**: Agent execution takes significant time (typically 10-30 minutes per phase, sometimes longer). The coordinator MUST:
+    - Wait patiently for `wait()` calls to complete
+    - NOT skip workflow steps due to perceived delays
+    - NOT assume agents have failed just because they're taking time
+    - Trust the timeout mechanisms defined in the skill
+
+17. **Use send_input for Clarification**: When agents need guidance or appear stuck, the coordinator MUST:
+    - Use `send_input()` to ask questions or provide clarification
+    - NOT skip the agent or move to next phase prematurely
+    - Give agents opportunity to respond before escalating
+    - Example: `send_input({ id: agent_id, message: "Please provide status update or clarify blockers" })`
+
+18. **No Workflow Shortcuts**: The coordinator MUST NOT:
+    - Skip phases or stages defined in the workflow
+    - Bypass required approval or review steps
+    - Execute dependent tasks before prerequisites complete
+    - Assume task completion without explicit agent callback
+    - Make up or fabricate agent results
+
+19. **Respect Long-Running Processes**: This is a complex multi-agent workflow that requires patience:
+    - Total execution time may range from 30-90 minutes or longer
+    - Each phase may take 10-30 minutes depending on complexity
+    - The coordinator must remain active and attentive throughout the entire process
+    - Do not terminate or skip steps due to time concerns

package/.codex/skills/team-coordinate/agents/completion-handler.md

@@ -34,7 +34,7 @@ Interactive agent for handling pipeline completion actions. Presents results sum
 | Tool | Type | Purpose |
 |------|------|---------|
 | `Read` | built-in | Load tasks.csv, artifacts |
-| `AskUserQuestion` | built-in | Get completion choice |
+| `request_user_input` | built-in | Get completion choice |
 | `Write` | built-in | Store completion result |
 | `Bash` | built-in | Archive or export operations |
 
@@ -74,11 +74,11 @@ Interactive agent for handling pipeline completion actions. Presents results sum
 1. Present completion choice:
 
 ```javascript
-AskUserQuestion({
+request_user_input({
   questions: [{
     question: "Team pipeline complete. What would you like to do?",
     header: "Completion",
-    multiSelect: false,
+    id: "completion_action",
     options: [
       { label: "Archive & Clean (Recommended)", description: "Mark session complete, output final summary" },
       { label: "Keep Active", description: "Keep session for follow-up work" },

package/.codex/skills/team-coordinate/agents/plan-reviewer.md

@@ -36,7 +36,7 @@ Interactive agent for reviewing and approving plans before execution waves. Used
 | Tool | Type | Purpose |
 |------|------|---------|
 | `Read` | built-in | Load plan artifacts and context |
-| `AskUserQuestion` | built-in | Get user approval or revision feedback |
+| `request_user_input` | built-in | Get user approval or revision feedback |
 | `Write` | built-in | Store review result |
 
 ### Tool Usage Patterns
@@ -89,13 +89,13 @@ Write("<session>/interactive/<task-id>-result.json", <result>)
 2. Present approval choice:
 
 ```javascript
-AskUserQuestion({
+request_user_input({
   questions: [{
     question: "Review the plan and decide:",
     header: "Plan Review",
-    multiSelect: false,
+    id: "plan_review",
     options: [
-      { label: "Approve", description: "Proceed with execution" },
+      { label: "Approve (Recommended)", description: "Proceed with execution" },
       { label: "Revise", description: "Request changes to the plan" },
       { label: "Abort", description: "Cancel the pipeline" }
     ]