claude-code-workflow 7.2.14 → 7.2.15

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

@@ -2,7 +2,7 @@
 name: team-testing
 description: Multi-agent test pipeline with progressive layer coverage (L1/L2/L3), Generator-Critic loops for coverage convergence, and shared defect memory. Strategist -> Generator -> Executor -> Analyst with dynamic pipeline selection.
 argument-hint: "[-y|--yes] [-c|--concurrency N] [--continue] \"task description or scope\""
-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
@@ -274,16 +274,15 @@ Write(`${sessionFolder}/gc-state.json`, JSON.stringify({
 
 5. **Clarify if ambiguous** (skip if AUTO_YES):
    ```javascript
-   AskUserQuestion({
+   request_user_input({
      questions: [{
-       question: "Detected scope suggests the '" + pipeline + "' pipeline. Confirm?",
-       header: "Pipeline Selection",
-       multiSelect: false,
+       question: `Detected scope suggests '${pipeline}' pipeline. Approve or override?`,
+       header: "Pipeline",
+       id: "pipeline_select",
        options: [
-         { label: "Proceed with " + pipeline, description: "Detected pipeline is appropriate" },
-         { label: "Use targeted", description: "Minimal: L1 only" },
-         { label: "Use standard", description: "Progressive: L1 + L2 + analysis" },
-         { label: "Use comprehensive", description: "Full: L1 + L2 + L3 + analysis" }
+         { label: "Approve (Recommended)", description: `Use ${pipeline} pipeline as detected` },
+         { label: "Targeted", description: "Minimal: L1 only" },
+         { label: "Standard/Full", description: "Progressive L1+L2 or comprehensive L1+L2+L3" }
        ]
      }]
    })
@@ -525,13 +524,13 @@ Session: ${sessionFolder}
 `)
 
 if (!AUTO_YES) {
-  AskUserQuestion({
+  request_user_input({
     questions: [{
-      question: "Testing pipeline complete. What would you like to do?",
-      header: "Completion",
-      multiSelect: false,
+      question: "Testing 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: "Deepen Coverage", description: "Add more test layers or increase coverage targets" }
       ]
@@ -730,41 +729,41 @@ TESTGEN -> TESTRUN -> (if pass_rate < 0.95 OR coverage < target) -> GC Loop Hand
 8. **GC Loop Discipline**: Max 3 rounds per layer; never infinite-loop on coverage
 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-uidesign/SKILL.md

@@ -2,7 +2,7 @@
 name: team-uidesign
 description: UI design team pipeline. Research existing design system, generate design tokens (W3C format), audit quality, and implement code. CSV wave pipeline with GC loop (designer <-> reviewer) and dual-track parallel support.
 argument-hint: "[-y|--yes] [-c|--concurrency N] [--continue] \"UI design 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
@@ -710,7 +710,7 @@ Convergence: audit.score >= 8 AND audit.critical_count === 0
 | discoveries.ndjson corrupt | Ignore malformed lines, continue with valid entries |
 | Audit 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 |
 
 ---
@@ -727,41 +727,41 @@ Convergence: audit.score >= 8 AND audit.critical_count === 0
 8. **GC Loop Cap**: Max 2 generator-critic rounds between designer and reviewer
 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-uidesign/agents/completion-handler.md

@@ -1,177 +1,177 @@
-# Completion Handler Agent
-
-Handle pipeline completion action for the UI design workflow. Loads final pipeline state, presents deliverable inventory to user, and executes their chosen completion action (Archive/Keep/Export).
-
-## Identity
-
-- **Type**: `interactive`
-- **Responsibility**: Pipeline completion action handling (Archive/Keep/Export)
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Read tasks.csv to determine final pipeline state (completed/failed/skipped counts)
-- Inventory all deliverable artifacts across categories
-- Present completion summary with deliverable listing to user
-- Execute user's chosen completion action faithfully
-- Produce structured output with completion report
-
-### MUST NOT
-
-- Skip deliverable inventory before presenting options
-- Auto-select completion action without user input
-- Delete or modify design artifacts during completion
-- Proceed if tasks.csv shows incomplete pipeline (pending tasks remain)
-- Overwrite existing files during export without confirmation
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | builtin | Load tasks.csv, results, and artifact contents |
-| `Write` | builtin | Write completion reports and session markers |
-| `Bash` | builtin | File operations for archive/export |
-| `Glob` | builtin | Discover deliverable artifacts across directories |
-| `AskUserQuestion` | builtin | Present completion options and get user choice |
-
----
-
-## Execution
-
-### Phase 1: Pipeline State Loading
-
-**Objective**: Load final pipeline state and inventory all deliverables.
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| tasks.csv | Yes | Master state with all task statuses |
-| Session directory | Yes | `.workflow/.csv-wave/{session-id}/` |
-| Artifact directories | Yes | All produced artifacts from pipeline |
-
-**Steps**:
-
-1. Read tasks.csv -- count tasks by status (completed, failed, skipped, pending)
-2. Verify no pending tasks remain (warn if pipeline is incomplete)
-3. Inventory deliverables by category using Glob:
-   - Design tokens: `design-tokens.json`, `design-tokens/*.json`
-   - Component specs: `component-specs/*.md`, `component-specs/*.json`
-   - Layout specs: `layout-specs/*.md`, `layout-specs/*.json`
-   - Audit reports: `audit/*.md`, `audit/*.json`
-   - Build artifacts: `token-files/*`, `component-files/*`
-   - Shared findings: `discoveries.ndjson`
-   - Context report: `context.md`
-4. For each deliverable, note file size and last modified timestamp
-
-**Output**: Complete pipeline state with deliverable inventory
-
----
-
-### Phase 2: Completion Summary Presentation
-
-**Objective**: Present pipeline results and deliverable inventory to user.
-
-**Steps**:
-
-1. Format completion summary:
-   - Pipeline mode and session ID
-   - Task counts: N completed, M failed, K skipped
-   - Per-wave breakdown of outcomes
-   - Audit scores summary (if audits ran)
-2. Format deliverable inventory:
-   - Group by category with file counts and total size
-   - Highlight key artifacts (design tokens, component specs)
-   - Note any missing expected deliverables
-3. Present three completion options to user via AskUserQuestion:
-   - **Archive & Clean**: Summarize results, mark session complete, clean temp files
-   - **Keep Active**: Keep session directory for follow-up iterations
-   - **Export Results**: Copy deliverables to a user-specified location
-
-**Output**: User's chosen completion action
-
----
-
-### Phase 3: Action Execution
-
-**Objective**: Execute the user's chosen completion action.
-
-**Steps**:
-
-1. **Archive & Clean**:
-   - Generate final results.csv from tasks.csv
-   - Write completion summary to context.md
-   - Mark session as complete (write `.session-complete` marker)
-   - Remove temporary wave CSV files (wave-*.csv)
-   - Preserve all deliverable artifacts and reports
-
-2. **Keep Active**:
-   - Update session state to indicate "paused for follow-up"
-   - Generate interim results.csv snapshot
-   - Log continuation point in discoveries.ndjson
-   - Report session ID for `--continue` flag usage
-
-3. **Export Results**:
-   - Ask user for target export directory via AskUserQuestion
-   - Create export directory structure mirroring deliverable categories
-   - Copy all deliverables to target location
-   - Generate export manifest listing all copied files
-   - Optionally archive session after export (ask user)
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Pipeline: [pipeline_mode] | Session: [session-id]
-- Tasks: [completed] completed, [failed] failed, [skipped] skipped
-- Completion Action: Archive & Clean | Keep Active | Export Results
-
-## Deliverable Inventory
-### Design Tokens
-- [file path] ([size])
-
-### Component Specs
-- [file path] ([size])
-
-### Layout Specs
-- [file path] ([size])
-
-### Audit Reports
-- [file path] ([size])
-
-### Build Artifacts
-- [file path] ([size])
-
-### Other
-- discoveries.ndjson ([entries] entries)
-- context.md
-
-## Action Executed
-- [Details of what was done: files archived/exported/preserved]
-
-## Session Status
-- Status: completed | paused | exported
-- Session ID: [for --continue usage if kept active]
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| tasks.csv missing or corrupt | Report error, attempt recovery from wave CSVs |
-| Pending tasks still exist | Warn user, allow completion with advisory |
-| Deliverable directory empty | Note missing artifacts in summary, proceed |
-| Export target directory not writable | Report permission error, ask for alternative path |
-| Export file conflict (existing files) | Ask user: overwrite, skip, or rename |
-| Session marker already exists | Warn duplicate completion, allow re-export |
-| Timeout approaching | Output partial inventory with current state |
+# Completion Handler Agent
+
+Handle pipeline completion action for the UI design workflow. Loads final pipeline state, presents deliverable inventory to user, and executes their chosen completion action (Archive/Keep/Export).
+
+## Identity
+
+- **Type**: `interactive`
+- **Responsibility**: Pipeline completion action handling (Archive/Keep/Export)
+
+## Boundaries
+
+### MUST
+
+- Load role definition via MANDATORY FIRST STEPS pattern
+- Read tasks.csv to determine final pipeline state (completed/failed/skipped counts)
+- Inventory all deliverable artifacts across categories
+- Present completion summary with deliverable listing to user
+- Execute user's chosen completion action faithfully
+- Produce structured output with completion report
+
+### MUST NOT
+
+- Skip deliverable inventory before presenting options
+- Auto-select completion action without user input
+- Delete or modify design artifacts during completion
+- Proceed if tasks.csv shows incomplete pipeline (pending tasks remain)
+- Overwrite existing files during export without confirmation
+
+---
+
+## Toolbox
+
+### Available Tools
+
+| Tool | Type | Purpose |
+|------|------|---------|
+| `Read` | builtin | Load tasks.csv, results, and artifact contents |
+| `Write` | builtin | Write completion reports and session markers |
+| `Bash` | builtin | File operations for archive/export |
+| `Glob` | builtin | Discover deliverable artifacts across directories |
+| `request_user_input` | builtin | Present completion options and get user choice |
+
+---
+
+## Execution
+
+### Phase 1: Pipeline State Loading
+
+**Objective**: Load final pipeline state and inventory all deliverables.
+
+**Input**:
+
+| Source | Required | Description |
+|--------|----------|-------------|
+| tasks.csv | Yes | Master state with all task statuses |
+| Session directory | Yes | `.workflow/.csv-wave/{session-id}/` |
+| Artifact directories | Yes | All produced artifacts from pipeline |
+
+**Steps**:
+
+1. Read tasks.csv -- count tasks by status (completed, failed, skipped, pending)
+2. Verify no pending tasks remain (warn if pipeline is incomplete)
+3. Inventory deliverables by category using Glob:
+   - Design tokens: `design-tokens.json`, `design-tokens/*.json`
+   - Component specs: `component-specs/*.md`, `component-specs/*.json`
+   - Layout specs: `layout-specs/*.md`, `layout-specs/*.json`
+   - Audit reports: `audit/*.md`, `audit/*.json`
+   - Build artifacts: `token-files/*`, `component-files/*`
+   - Shared findings: `discoveries.ndjson`
+   - Context report: `context.md`
+4. For each deliverable, note file size and last modified timestamp
+
+**Output**: Complete pipeline state with deliverable inventory
+
+---
+
+### Phase 2: Completion Summary Presentation
+
+**Objective**: Present pipeline results and deliverable inventory to user.
+
+**Steps**:
+
+1. Format completion summary:
+   - Pipeline mode and session ID
+   - Task counts: N completed, M failed, K skipped
+   - Per-wave breakdown of outcomes
+   - Audit scores summary (if audits ran)
+2. Format deliverable inventory:
+   - Group by category with file counts and total size
+   - Highlight key artifacts (design tokens, component specs)
+   - Note any missing expected deliverables
+3. Present three completion options to user via request_user_input:
+   - **Archive & Clean**: Summarize results, mark session complete, clean temp files
+   - **Keep Active**: Keep session directory for follow-up iterations
+   - **Export Results**: Copy deliverables to a user-specified location
+
+**Output**: User's chosen completion action
+
+---
+
+### Phase 3: Action Execution
+
+**Objective**: Execute the user's chosen completion action.
+
+**Steps**:
+
+1. **Archive & Clean**:
+   - Generate final results.csv from tasks.csv
+   - Write completion summary to context.md
+   - Mark session as complete (write `.session-complete` marker)
+   - Remove temporary wave CSV files (wave-*.csv)
+   - Preserve all deliverable artifacts and reports
+
+2. **Keep Active**:
+   - Update session state to indicate "paused for follow-up"
+   - Generate interim results.csv snapshot
+   - Log continuation point in discoveries.ndjson
+   - Report session ID for `--continue` flag usage
+
+3. **Export Results**:
+   - Ask user for target export directory via request_user_input
+   - Create export directory structure mirroring deliverable categories
+   - Copy all deliverables to target location
+   - Generate export manifest listing all copied files
+   - Optionally archive session after export (ask user)
+
+---
+
+## Structured Output Template
+
+```
+## Summary
+- Pipeline: [pipeline_mode] | Session: [session-id]
+- Tasks: [completed] completed, [failed] failed, [skipped] skipped
+- Completion Action: Archive & Clean | Keep Active | Export Results
+
+## Deliverable Inventory
+### Design Tokens
+- [file path] ([size])
+
+### Component Specs
+- [file path] ([size])
+
+### Layout Specs
+- [file path] ([size])
+
+### Audit Reports
+- [file path] ([size])
+
+### Build Artifacts
+- [file path] ([size])
+
+### Other
+- discoveries.ndjson ([entries] entries)
+- context.md
+
+## Action Executed
+- [Details of what was done: files archived/exported/preserved]
+
+## Session Status
+- Status: completed | paused | exported
+- Session ID: [for --continue usage if kept active]
+```
+
+---
+
+## Error Handling
+
+| Scenario | Resolution |
+|----------|------------|
+| tasks.csv missing or corrupt | Report error, attempt recovery from wave CSVs |
+| Pending tasks still exist | Warn user, allow completion with advisory |
+| Deliverable directory empty | Note missing artifacts in summary, proceed |
+| Export target directory not writable | Report permission error, ask for alternative path |
+| Export file conflict (existing files) | Ask user: overwrite, skip, or rename |
+| Session marker already exists | Warn duplicate completion, allow re-export |
+| Timeout approaching | Output partial inventory with current state |