The user, on work 52, after I parked the chat-window planning to wait for three answers:
"why do you park this work, and why don't you just start planning? Maybe something in our
flow is wrong... we should find a solution so that the agent will not start parking when
auto mode is on. Parking a to-do means that it is meant to be executed after or later.
Parking something is meant for 'Oh shit, I will do something in the meantime,' or 'Hey,
I'm stuck,' etc. This should be taught to the agents very well."

The error it names: I read "shape the goal with the user before drafting" as "stop and
wait for answers". But a plan is a DRAFT until the user approves it in the viewer — the
draft IS the shaping artifact, and it asks the question better than a question does,
because the user corrects a sentence instead of answering three. Waiting first bought
nothing except their time.

The test before parking: is there something I could still be DOING? If yes, do it, and let
the artifact carry the question. Parking is for when the answer is genuinely the only thing
that unblocks the next keystroke, or when something else has to happen first. Under auto
mode it is worse than idle: the list stops.