claude-code-workflow 7.2.14 → 7.2.15

package/.codex/skills/team-designer/agents/requirement-clarifier.md

@@ -36,7 +36,7 @@ Interactive agent for gathering and refining team skill requirements from user i
 | Tool | Type | Purpose |
 |------|------|---------|
 | `Read` | built-in | Load reference skills, existing patterns |
-| `AskUserQuestion` | built-in | Gather missing details from user |
+| `request_user_input` | built-in | Gather missing details from user |
 | `Write` | built-in | Store teamConfig.json |
 | `Glob` | built-in | Find reference skill files |
 
@@ -94,23 +94,23 @@ Write("<session>/teamConfig.json", <config>)
 1. **Core Identity** -- gather if not clear from input:
 
 ```javascript
-AskUserQuestion({
+request_user_input({
   questions: [
     {
       question: "Team skill name? (kebab-case, e.g., team-code-review)",
       header: "Skill Name",
-      multiSelect: false,
+      id: "skill_name",
       options: [
-        { label: "<auto-suggested-name>", description: "Auto-suggested from description" },
+        { label: "<auto-suggested-name> (Recommended)", description: "Auto-suggested from description" },
         { label: "Custom", description: "Enter custom name" }
       ]
     },
     {
       question: "Session prefix? (3-4 chars for task IDs, e.g., TCR)",
       header: "Prefix",
-      multiSelect: false,
+      id: "session_prefix",
       options: [
-        { label: "<auto-suggested-prefix>", description: "Auto-suggested" },
+        { label: "<auto-suggested-prefix> (Recommended)", description: "Auto-suggested" },
         { label: "Custom", description: "Enter custom prefix" }
       ]
     }
@@ -186,16 +186,15 @@ Templates: <list or none>
 2. Present confirmation:
 
 ```javascript
-AskUserQuestion({
+request_user_input({
   questions: [{
     question: "Confirm this team skill configuration?",
-    header: "Configuration Review",
-    multiSelect: false,
+    header: "Config Review",
+    id: "config_review",
     options: [
-      { label: "Confirm", description: "Proceed with generation" },
+      { label: "Confirm (Recommended)", description: "Proceed with generation" },
       { label: "Modify Roles", description: "Add, remove, or change roles" },
-      { label: "Modify Pipelines", description: "Change pipeline structure" },
-      { label: "Cancel", description: "Abort skill generation" }
+      { label: "Modify Pipelines", description: "Change pipeline structure" }
     ]
   }]
 })

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

@@ -2,7 +2,7 @@
 name: team-executor
 description: Lightweight session execution skill. Resumes existing team-coordinate sessions for pure execution via worker agents. No analysis, no role generation -- only loads and executes. Session path required.
 argument-hint: "[-y|--yes] [-c|--concurrency N] [--continue] \"--session=<path>\""
-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
@@ -383,13 +383,13 @@ const summary = {
 console.log(`Pipeline complete: ${summary.completed}/${summary.total} tasks completed`)
 
 // Completion action
-const action = await AskUserQuestion({
+const action = 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, clean up team" },
+      { label: "Archive (Recommended)", description: "Archive session, clean up team" },
       { label: "Keep Active", description: "Keep session for follow-up work" },
       { label: "Export Results", description: "Export deliverables to target directory, then clean" }
     ]
@@ -397,7 +397,7 @@ const action = await AskUserQuestion({
 })
 
 // Handle completion action
-if (action === "Archive & Clean") {
+if (action.answers.completion.answers[0] === "Archive (Recommended)") {
   // Update session status, cleanup team
 } else if (action === "Keep Active") {
   // Update session status to paused
@@ -475,41 +475,41 @@ if (action === "Archive & Clean") {
 8. **Lifecycle Balance**: Every spawn_agent MUST have a matching close_agent (tracked in registry.json)
 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-frontend/SKILL.md

@@ -2,7 +2,7 @@
 name: team-frontend
 description: Frontend development team with built-in ui-ux-pro-max design intelligence. Covers requirement analysis, design system generation, frontend implementation, and quality assurance. CSV wave pipeline with interactive QA gates.
 argument-hint: "[-y|--yes] [-c|--concurrency N] [--continue] \"frontend 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
@@ -535,13 +535,13 @@ ${deliverables.map(d => `  - ${d.name}: ${d.path}`).join('\n')}
 `)
 
 if (!AUTO_YES) {
-  AskUserQuestion({
+  request_user_input({
     questions: [{
-      question: "Frontend pipeline complete. What would you like to do?",
-      header: "Completion",
-      multiSelect: false,
+      question: "Frontend 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: "Export Results", description: "Export design tokens and component specs" }
       ]
@@ -693,7 +693,7 @@ Convergence: qa.score >= 8 && qa.critical_count === 0
 | discoveries.ndjson corrupt | Ignore malformed lines, continue with valid entries |
 | QA score < 6 over 2 GC rounds | Escalate to user for manual intervention |
 | ui-ux-pro-max unavailable | Degrade to LLM general design knowledge |
-| 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 |
 
 ---
@@ -710,41 +710,41 @@ Convergence: qa.score >= 8 && qa.critical_count === 0
 8. **GC Loop Cap**: Max 2 generator-critic rounds between developer and qa
 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-frontend/agents/completion-handler.md

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

package/.codex/skills/team-frontend/agents/qa-gate-reviewer.md

@@ -36,7 +36,7 @@ Interactive agent for reviewing QA audit verdicts and handling the Generator-Cri
 | Tool | Type | Purpose |
 |------|------|---------|
 | `Read` | built-in | Load QA audit reports and context |
-| `AskUserQuestion` | built-in | Get user decision on QA gate |
+| `request_user_input` | built-in | Get user decision on QA gate |
 | `Write` | built-in | Store review result |
 
 ### Tool Usage Patterns
@@ -97,13 +97,13 @@ Write("<session>/interactive/<task-id>-result.json", <result>)
 2. If escalation needed, present choice:
 
 ```javascript
-AskUserQuestion({
+request_user_input({
   questions: [{
     question: "QA has flagged issues after 2 fix rounds. How would you like to proceed?",
     header: "QA Gate",
-    multiSelect: false,
+    id: "qa_gate_decision",
     options: [
-      { label: "Accept current state", description: "Proceed despite remaining issues" },
+      { label: "Accept current state (Recommended)", description: "Proceed despite remaining issues" },
       { label: "Manual fix", description: "You will fix the issues manually" },
       { label: "Abort pipeline", description: "Stop the pipeline" }
     ]

package/.codex/skills/team-frontend-debug/SKILL.md

@@ -2,7 +2,7 @@
 name: team-frontend-debug
 description: Frontend debugging team using Chrome DevTools MCP. Dual-mode -- feature-list testing or bug-report debugging. Covers reproduction, root cause analysis, code fixes, and verification. CSV wave pipeline with conditional skip and iteration loops.
 argument-hint: "[-y|--yes] [-c|--concurrency N] [--continue] \"feature list or bug 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
@@ -98,7 +98,7 @@ Dual-mode frontend debugging: feature-list testing or bug-report debugging, powe
 | feature, test, list, check, verify functions, validate | `test-pipeline` |
 | bug, error, crash, broken, white screen, not working | `debug-pipeline` |
 | performance, slow, latency, memory leak | `debug-pipeline` (perf dimension) |
-| Ambiguous / unclear | AskUserQuestion to clarify |
+| Ambiguous / unclear | request_user_input to clarify |
 
 ---
 
@@ -305,19 +305,19 @@ Write(`${sessionFolder}/wisdom/learnings.md`, '# Debug Learnings\n')
    |---------------|------|
    | Contains: feature, test, list, check, verify | `test-pipeline` |
    | Contains: bug, error, crash, broken, not working | `debug-pipeline` |
-   | Ambiguous | AskUserQuestion to clarify |
+   | Ambiguous | request_user_input to clarify |
 
 4. **Extract parameters by mode**:
 
    **Test Mode**:
-   - `base_url`: URL in text or AskUserQuestion
+   - `base_url`: URL in text or request_user_input
    - `features`: Parse feature list (bullet points, numbered list, free text)
    - Generate structured feature items with id, name, url
 
    **Debug Mode**:
    - `bug_description`: Bug description text
-   - `target_url`: URL in text or AskUserQuestion
-   - `reproduction_steps`: Steps in text or AskUserQuestion
+   - `target_url`: URL in text or request_user_input
+   - `reproduction_steps`: Steps in text or request_user_input
    - `evidence_plan`: Detect dimensions from keywords (UI, network, console, performance)
 
 5. **Dimension Detection** (debug mode):
@@ -616,13 +616,13 @@ ${completed.map(t => `  [DONE] ${t.id} (${t.role}): ${t.findings?.substring(0, 8
 `)
 
 if (!AUTO_YES) {
-  AskUserQuestion({
+  request_user_input({
     questions: [{
-      question: "Debug pipeline complete. What would you like to do?",
-      header: "Completion",
-      multiSelect: false,
+      question: "Debug 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 debugging" },
         { label: "Export Results", description: "Export debug report and patches" }
       ]
@@ -732,7 +732,7 @@ After TEST-001 completes, evaluate issues:
 | Condition | Action |
 |-----------|--------|
 | `issues_count === 0` | Skip ANALYZE/FIX/VERIFY. Pipeline complete with all-pass. |
-| Only low-severity warnings | AskUserQuestion: fix warnings or complete |
+| Only low-severity warnings | request_user_input: fix warnings or complete |
 | High/medium severity issues | Proceed with ANALYZE -> FIX -> VERIFY |
 
 ---
@@ -781,41 +781,41 @@ After TEST-001 completes, evaluate issues:
 9. **Iteration Bounds**: Max 2 reproduction rounds, max 3 fix rounds
 10. **Cleanup Temp Files**: Remove wave-{N}.csv after results are merged
 11. **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-frontend-debug/agents/completion-handler.md

@@ -34,7 +34,7 @@ Interactive agent for handling pipeline completion action. Presents debug summar
 | Tool | Type | Purpose |
 |------|------|---------|
 | `Read` | built-in | Load task results and artifacts |
-| `AskUserQuestion` | built-in | Get user completion choice |
+| `request_user_input` | built-in | Get user completion choice |
 | `Write` | built-in | Store completion result |
 | `Bash` | built-in | Execute archive/export operations |
 
@@ -79,11 +79,11 @@ Interactive agent for handling pipeline completion action. Presents debug summar
 2. Present completion choice:
 
 ```javascript
-AskUserQuestion({
+request_user_input({
   questions: [{
     question: "Debug pipeline complete. What would you like to do?",
     header: "Completion",
-    multiSelect: false,
+    id: "completion_action",
     options: [
       { label: "Archive & Clean (Recommended)", description: "Archive session, output final summary" },
       { label: "Keep Active", description: "Keep session for follow-up debugging" },

package/.codex/skills/team-frontend-debug/agents/conditional-skip-gate.md

@@ -35,7 +35,7 @@ Interactive agent for evaluating TEST-001 results and determining whether to ski
 | Tool | Type | Purpose |
 |------|------|---------|
 | `Read` | built-in | Load test results and issues |
-| `AskUserQuestion` | built-in | Get user decision on warnings |
+| `request_user_input` | built-in | Get user decision on warnings |
 | `Write` | built-in | Store gate decision result |
 
 ---
@@ -81,13 +81,13 @@ Interactive agent for evaluating TEST-001 results and determining whether to ski
 2. If only warnings, present choice:
 
 ```javascript
-AskUserQuestion({
+request_user_input({
   questions: [{
     question: "Testing found only low-severity warnings. How would you like to proceed?",
     header: "Test Results",
-    multiSelect: false,
+    id: "warning_decision",
     options: [
-      { label: "Fix warnings", description: "Proceed with analysis and fixes for warnings" },
+      { label: "Fix warnings (Recommended)", description: "Proceed with analysis and fixes for warnings" },
       { label: "Complete", description: "Accept current state, skip remaining tasks" }
     ]
   }]