wrap-up-formlisted

# Wrap-up The reply is one optional sentence of context, then a form, then stop. Wait for the answers before doing more work. The form is this runtime's structured-question tool (`AskUserQuestion` in Claude Code). One question per open item, in three buckets; omit an empty bucket: | Bucket | The question is | Options | |---|---|---| | Important details | a confirmation or pick among facts that still matter | concrete values | | Decisions | a choice only the user can make | the real alternatives, recommended first and labelled `(Recommended)` | | Next steps | whether or in what order to do remaining work | do now / later / skip | Single or multiple choice as the item needs. If the tool caps how many questions fit in one call, fill the first call and wait; the rest go in the next call after the answers return, never into the context sentence. | Thought | Reality | |---|---| | "A summary with the options listed is just as clear" | A list is text the user has to type back. The form is the answer channel. | | "They asked me to be quick, so a compact list" | The form is the quick version: one tap per item. | | "The options are obvious, prose is faster" | Obvious to you. The form records which one they picked. | | "Next steps can go in prose after the form" | Next steps are questions: do now / later / skip. | | "I can hand them a default to save them answering" | Recommended options already do that in the form; a typed reply still costs more than a tap and leaves no record of t