execute-plan-tasks

# Execute plan tasks One task per run — implement it, verify it, tick it, stop. The review between tasks is the point; never carry on into the next. Invocation: `/execute-plan-tasks <plan-path> [task-id]` ## Pick the task Read the plan whole — summary, conventions and overrides, the steps the task cites, acceptance criteria — then its `## Tasks` section. Ambiguous or missing plan path → ask. Several task sections → ask which one this run works from. No task section → stop and point at `/split-plan-tasks`. `task-id` given → that task; none → the first unticked one in order. A range or a whole group → run its first task only, saying the rest need their own runs; a task already ticked → say so and ask whether to redo it. Its dependencies — earlier tasks in its group, plus every task in each group its *Depends on* line names — must be ticked; name any unticked dependency and ask before proceeding. Done when the chosen task, its steps, its acceptance criteria and its dependency state are stated. ## Execute - **Scope is the task's steps, nothing else**: no work belonging to a later task, no drive-by refactors. Work the plan calls for that no task covers → report it, don't absorb it. - The plan's conventions and overrides bind every task, this one included. - **Never guess.** What the code settles, settle by reading it; what it doesn't goes to the user as one question carrying your recommendation. Append each settled deviation from the plan, and its why, as one line to...