Run Tasks

If the user has only invoked /run-tasks, begin with a short natural prompt such as:

• 你是想跑单个 task，还是跑当前全部 active tasks？

Intake method

Use AskUserQuestion only to clarify execution choices such as:

• run one task or all active tasks
• whether the default retry count of 3 should be overridden
• whether the user is intentionally previewing the prompt rather than executing

Do not turn this skill into a deep requirements interview.

Execution model

The runner is not a plain shell loop. It must:

• create a fresh git worktree per attempt
• launch a fresh Claude Code session per attempt
• inject local failure summaries into retries
• optionally append external diagnostic summaries
• run the verify gate before considering a task complete

Preferred commands

• List tasks: ./task-runner.sh list
• Preview prompt: ./task-runner.sh prompt --task <path>
• Run one task: ./task-runner.sh run --task <path>
• Run all tasks: ./task-runner.sh run-all
• Default retry count is 3 unless the user asks otherwise

Rules

• Preserve progressive disclosure; do not bypass the runner by manually reconstructing the task loop.
• Treat successful worktrees as reviewable by default.
• Failed attempts should be cleaned up by the runner.
• If the repository is not clean, explain that runner preflight will block execution until the user commits or stashes changes.