claude-code-workflow 7.2.14 → 7.2.15

package/.codex/skills/team-quality-assurance/SKILL.md

@@ -2,7 +2,7 @@
 name: team-quality-assurance
 description: Full closed-loop QA combining issue discovery and software testing. Scout -> Strategist -> Generator -> Executor -> Analyst with multi-perspective scanning, progressive test layers, GC loops, and quality scoring. Supports discovery, testing, and full QA modes.
 argument-hint: "[-y|--yes] [-c|--concurrency N] [--continue] [--mode=discovery|testing|full] \"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
@@ -286,16 +286,15 @@ Write(`${sessionFolder}/gc-state.json`, JSON.stringify({
 
 4. **Clarify if ambiguous** (skip if AUTO_YES):
    ```javascript
-   AskUserQuestion({
+   request_user_input({
      questions: [{
-       question: "Detected QA mode: '" + qaMode + "'. Confirm?",
-       header: "QA Mode Selection",
-       multiSelect: false,
+       question: `Detected QA mode: '${qaMode}'. Approve or override?`,
+       header: "QA Mode",
+       id: "qa_mode",
        options: [
-         { label: "Proceed with " + qaMode, description: "Detected mode is appropriate" },
-         { label: "Use discovery", description: "Scout-first: scan for issues, then test" },
-         { label: "Use testing", description: "Direct testing pipeline (skip scout)" },
-         { label: "Use full", description: "Complete QA closed loop with regression" }
+         { label: "Approve (Recommended)", description: `Use ${qaMode} mode as detected` },
+         { label: "Discovery", description: "Scout-first: scan for issues, then test" },
+         { label: "Testing/Full", description: "Direct testing or complete QA closed loop" }
        ]
      }]
    })
@@ -536,13 +535,13 @@ Session: ${sessionFolder}
 `)
 
 if (!AUTO_YES) {
-  AskUserQuestion({
+  request_user_input({
     questions: [{
-      question: "Quality Assurance pipeline complete. What would you like to do?",
-      header: "Completion",
-      multiSelect: false,
+      question: "Quality Assurance 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 deliverables to target directory" }
       ]
@@ -774,41 +773,41 @@ QAGEN -> QARUN -> (if coverage < target) -> GC Loop Handler
 9. **Scout Feeds Strategy**: Scout findings flow into strategist via prev_context and discoveries.ndjson
 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-review/SKILL.md

@@ -2,7 +2,7 @@
 name: team-review
 description: Multi-agent code review pipeline with scanner, reviewer, and fixer roles. Executes toolchain + LLM scan, deep analysis with root cause enrichment, and automated fixes with rollback-on-failure.
 argument-hint: "[-y|--yes] [-c|--concurrency N] [--continue] [--full|--fix|-q] [--dimensions=sec,cor,prf,mnt] \"target path or pattern\""
-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
@@ -476,7 +476,7 @@ send_input({
 | discoveries.ndjson corrupt | Ignore malformed lines, continue with valid entries |
 | Lifecycle leak | Cleanup all active agents via registry.json at end |
 | Continue mode: no session found | List available sessions, prompt user to select |
-| Target path invalid | AskUserQuestion for corrected path |
+| Target path invalid | request_user_input for corrected path |
 | Scanner finds 0 findings | Report clean, skip review + fix stages |
 
 ---
@@ -493,41 +493,41 @@ send_input({
 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-roadmap-dev/SKILL.md

@@ -2,7 +2,7 @@
 name: team-roadmap-dev
 description: Roadmap-driven development with phased execution pipeline. Coordinator discusses roadmap with user, then executes plan->execute->verify cycles per phase using CSV wave execution.
 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
@@ -244,7 +244,7 @@ const discusser = spawn_agent({
 
 **Instructions**:
 1. Analyze task description to understand scope
-2. Propose phase breakdown to user via AskUserQuestion
+2. Propose phase breakdown to user via request_user_input
 3. For each phase, clarify requirements and success criteria
 4. Generate roadmap.md with structured phase definitions
 5. Output result as JSON with roadmap_path and phase_count`
@@ -343,19 +343,19 @@ writeMasterCSV(`${sessionDir}/tasks.csv`, tasksWithWaves)
 
 // User validation (skip if autoYes)
 if (!autoYes) {
-  const approval = AskUserQuestion({
+  const approval = request_user_input({
     questions: [{
       question: `Generated ${tasksWithWaves.length} tasks across ${phases.length} phases. Proceed?`,
-      header: "Task Breakdown Validation",
-      multiSelect: false,
+      header: "Validate",
+      id: "task_approval",
       options: [
-        { label: "Proceed", description: "Start execution" },
+        { label: "Proceed (Recommended)", description: "Start execution" },
         { label: "Cancel", description: "Abort workflow" }
       ]
     }]
   })
 
-  if (approval.answers[0] !== "Proceed") {
+  if (approval.answers.task_approval.answers[0] !== "Proceed (Recommended)") {
     throw new Error("User cancelled workflow")
   }
 }
@@ -554,20 +554,20 @@ console.log(`\nResults: ${sessionDir}/results.csv`)
 console.log(`Report: ${sessionDir}/context.md`)
 
 // Offer next steps
-const nextStep = AskUserQuestion({
+const nextStep = request_user_input({
   questions: [{
-    question: "Roadmap Dev pipeline complete. What would you like to do?",
-    header: "Completion",
-    multiSelect: false,
+    question: "Roadmap Dev pipeline complete. Choose next action.",
+    header: "Done",
+    id: "completion",
     options: [
-      { label: "Archive & Clean (Recommended)", description: "Archive session, clean up tasks and team resources" },
+      { label: "Archive (Recommended)", description: "Archive session, clean up tasks and team resources" },
       { label: "Keep Active", description: "Keep session active for follow-up work or inspection" },
       { label: "Export Results", description: "Export deliverables to a specified location, then clean" }
     ]
   }]
 })
 
-if (nextStep.answers[0] === "Archive & Clean (Recommended)") {
+if (nextStep.answers.completion.answers[0] === "Archive (Recommended)") {
   Bash(`tar -czf "${sessionDir}.tar.gz" "${sessionDir}" && rm -rf "${sessionDir}"`)
   console.log(`Session archived to ${sessionDir}.tar.gz`)
 }
@@ -643,41 +643,41 @@ const discoveries = Read(`${sessionDir}/discoveries.ndjson`)
 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-roadmap-dev/agents/roadmap-discusser.md

@@ -14,7 +14,7 @@ Interactive agent for discussing roadmap with user and generating phase plan wit
 
 - Load role definition via MANDATORY FIRST STEPS pattern
 - Produce structured output following template
-- Interact with user via AskUserQuestion
+- Interact with user via request_user_input
 - Generate roadmap.md with phase definitions
 - Include requirements (REQ-IDs) and success criteria per phase
 
@@ -33,7 +33,7 @@ Interactive agent for discussing roadmap with user and generating phase plan wit
 
 | Tool | Type | Purpose |
 |------|------|---------|
-| `AskUserQuestion` | Human interaction | Clarify requirements, propose phase breakdown |
+| `request_user_input` | Human interaction | Clarify requirements, propose phase breakdown |
 | `Read` | File I/O | Load project context |
 | `Write` | File I/O | Generate roadmap.md |
 
@@ -81,15 +81,15 @@ Interactive agent for discussing roadmap with user and generating phase plan wit
    - Phase goal (one sentence)
    - Key requirements (REQ-IDs)
    - Success criteria (measurable)
-4. Present to user via AskUserQuestion:
+4. Present to user via request_user_input:
    ```javascript
-   AskUserQuestion({
+   request_user_input({
      questions: [{
        question: "Proposed phase breakdown:\n\nPhase 1: [goal]\n- REQ-001: [requirement]\n- Success: [criteria]\n\nPhase 2: [goal]\n...\n\nApprove or request changes?",
-       header: "Roadmap Discussion",
-       multiSelect: false,
+       header: "Roadmap",
+       id: "roadmap_approval",
        options: [
-         { label: "Approve", description: "Proceed with this breakdown" },
+         { label: "Approve (Recommended)", description: "Proceed with this breakdown" },
          { label: "Modify", description: "Request changes to phases" },
          { label: "Cancel", description: "Abort workflow" }
        ]
@@ -173,4 +173,4 @@ Interactive agent for discussing roadmap with user and generating phase plan wit
 | User cancels | Output partial roadmap, mark as cancelled |
 | Project context not found | Continue without project context, note in findings |
 | User requests too many phases (>10) | Warn about complexity, suggest consolidation |
-| Ambiguous requirements | Ask clarifying questions via AskUserQuestion |
+| Ambiguous requirements | Ask clarifying questions via request_user_input |

package/.codex/skills/team-tech-debt/SKILL.md

@@ -2,7 +2,7 @@
 name: team-tech-debt
 description: Systematic tech debt governance with CSV wave pipeline. Scans codebase for tech debt across 5 dimensions, assesses severity with priority matrix, plans phased remediation, executes fixes in worktree, validates with 4-layer checks. Supports scan/remediate/targeted pipeline modes with fix-verify GC loop.
 argument-hint: "[-y|--yes] [-c|--concurrency N] [--continue] [--mode=scan|remediate|targeted] \"scope or 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
@@ -259,13 +259,13 @@ Write(`${sessionFolder}/wisdom/decisions.md`, '# Decisions\n')
 
 2. **Clarify scope** (skip if AUTO_YES):
    ```javascript
-   AskUserQuestion({
+   request_user_input({
      questions: [{
-       question: "Tech debt governance scope:",
-       header: "Scope Selection",
-       multiSelect: false,
+       question: "Select tech debt governance scope.",
+       header: "Scope",
+       id: "debt_scope",
        options: [
-         { label: "Full project scan", description: "Scan entire codebase" },
+         { label: "Full scan (Recommended)", description: "Scan entire codebase" },
          { label: "Specific module", description: "Target specific directory" },
          { label: "Custom scope", description: "Specify file patterns" }
        ]
@@ -517,15 +517,15 @@ Session: ${sessionFolder}
 
 // Completion action
 if (!AUTO_YES) {
-  AskUserQuestion({
+  request_user_input({
     questions: [{
-      question: "What next?",
-      header: "Completion",
-      multiSelect: false,
+      question: "Tech debt governance complete. Choose next action.",
+      header: "Done",
+      id: "completion",
       options: [
+        { label: "Close (Recommended)", description: "Archive session" },
         { label: "New target", description: "Run another scan/fix cycle" },
-        { label: "Deep fix", description: "Continue fixing remaining items" },
-        { label: "Close", description: "Archive session" }
+        { label: "Deep fix", description: "Continue fixing remaining items" }
       ]
     }]
   })
@@ -668,41 +668,41 @@ Wave 3: TDVAL-001 (validator) -> 4-layer validation
 8. **GC Loop Bounded**: Maximum 3 fix-verify rounds before accepting current state
 9. **Worktree Isolation**: All fix execution happens in git worktree, not main branch
 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-tech-debt/agents/plan-approver.md

@@ -36,7 +36,7 @@ Interactive agent for reviewing the tech debt remediation plan at the plan appro
 | Tool | Type | Purpose |
 |------|------|---------|
 | `Read` | built-in | Load plan artifacts and context |
-| `AskUserQuestion` | built-in | Get user approval decision |
+| `request_user_input` | built-in | Get user approval decision |
 | `Write` | built-in | Store approval result |
 
 ### Tool Usage Patterns
@@ -91,13 +91,13 @@ Read("<session>/assessment/priority-matrix.json")
 2. Present decision:
 
 ```javascript
-AskUserQuestion({
+request_user_input({
   questions: [{
     question: "Remediation plan generated. Review and decide:",
-    header: "Plan Approval Gate",
-    multiSelect: false,
+    header: "Plan Approval",
+    id: "plan_approval",
     options: [
-      { label: "Approve", description: "Proceed with fix execution in worktree" },
+      { label: "Approve (Recommended)", description: "Proceed with fix execution in worktree" },
       { label: "Revise", description: "Re-run planner with specific feedback" },
       { label: "Abort", description: "Stop pipeline, keep scan/assessment results" }
     ]