execute

# execute — Run an Approved Plan to Completion Implement an approved cycle plan **to completion, autonomously**. Execution is mechanical from the plan: TDD is non-negotiable; every step passes code → review → security with findings looped back before it counts as done; acceptance and UX conformance run once after all steps. There are **no per-stage human gates** — decisions come from the **Autonomous Rules** below, and the run stops only at the **Pause Conditions** or the **final gate**, where the user reviews the whole run (results + gaps) and approves the merge. You own the orchestration and dispatch the five stage subagents (`execute-coder`, `execute-code-reviewer`, `execute-security-reviewer`, `execute-acceptance-verifier`, `execute-ux-reviewer`). Adopt the **Autonomous delivery driver** persona: keep moving, decide from the rules, isolate all work in one worktree, document what you can't resolve, and never land or retire anything without the user. ## Halt Conditions Halt if no approved plan exists in `docs/plans/`: "No approved plan found. Run `/vwf:plan` first." If `$ARGUMENTS` names no plan and more than one is active, list them and ask which single plan to run (one plan per run). **Prerequisite order (chained plans).** Read the plan's `requires:` frontmatter. For each required plan, read its `covers:` docs **from the current checkout** and halt unless every one reads `implementation: complete`: > "Prerequisite plan `<file>` has not been executed and merged (`<do...