execute

Auto Mode

When --yes or -y: Auto-confirm execution, use recommended settings.

Issue Execute Command (/issue:execute)

Overview

Minimal orchestrator that dispatches solution IDs to executors. Each executor receives a complete solution with all its tasks.

Design Principles:

• queue dag → returns parallel batches with solution IDs (S-1, S-2, ...)
• detail <id> → READ-ONLY solution fetch (returns full solution with all tasks)
• done <id> → update solution completion status
• No race conditions: status changes only via done
• Executor handles all tasks within a solution sequentially
• Single worktree for entire queue: One worktree isolates ALL queue execution from main workspace

Queue ID Requirement (MANDATORY)

Queue ID is REQUIRED. You MUST specify which queue to execute via --queue <queue-id>.

If Queue ID Not Provided

When --queue parameter is missing, you MUST:

1. List available queues by running:

const result = Bash('ccw issue queue list --brief --json');
const index = JSON.parse(result);

1. Display available queues to user:

Available Queues:
ID                    Status      Progress    Issues
-----------------------------------------------------------
→ QUE-20251215-001   active      3/10        ISS-001, ISS-002
  QUE-20251210-002   active      0/5         ISS-003
  QUE-20251205-003   completed   8/8         ISS-004

1. Stop and ask user to specify which queue to execute:

AskUserQuestion({
  questions: [{
    question: "Which queue would you like to execute?",
    header: "Queue",
    multiSelect: false,
    options: index.queues
      .filter(q => q.status === 'active')
      .map(q => ({
        label: q.id,
        description: `${q.status}, ${q.completed_solutions || 0}/${q.total_solutions || 0} completed, Issues: ${q.issue_ids.join(', ')}`
      }))
  }]
})

1. After user selection, continue execution with the selected queue ID.

DO NOT auto-select queues. Explicit user confirmation is required to prevent accidental execution of wrong queue.