executelisted

Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md). Read a plan, execute it fully. Execution is always automatic — never ask "proceed?" or "start?" during implementation. The user invoked execute; that IS the go-ahead. > **Live Unity editing during execution**: if a plan step needs to poke the live Unity Editor (inspect a component, modify a scene object, invoke a runtime method) instead of writing new C# code, consult [`shared/tykit-reference.md`](../../shared/tykit-reference.md) for the command map. Use tykit commands directly via the MCP tools (`unity_query`, `unity_object`, `unity_assets`, `unity_physics`) or direct HTTP (`/ping`, `/health`, `/focus-unity` for recovery). Only fall back to code-writing for changes that need version control or compile-time validation. Arguments: $ARGUMENTS - A file path to a plan/design document - `--no-worktree`: skip worktree guard - `--auto`: after completion, auto-select and run the next workflow step instead of asking the user (includes push — user should be aware) - No arguments: detect the plan source from conversation or `Docs/qq/` ## 1. Worktree Guard (strict — do NOT bypass) **Worktree isolation is non-negotiable for `/qq:execute`.** Executing a multi-step plan directly on a shared branch pollutes main, blocks parallel work, and makes rollback surgical instead of trivial. You MUST enter a worktree unless one of these **three** conditions is explicitl