[FEATURE] Collapsible / minimizable AskUserQuestion widget

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When Claude uses the AskUserQuestion tool inside a multi-step skill flow, the widget renders as a large, persistent block at the bottom of the screen. If the previous assistant turn produced meaningful output — a results table, field values, a success/error message — that content gets pushed out of view the moment the widget appears. The user has to scroll up to read it, but the widget remains blocking the screen and there is no way to temporarily hide it. Dismissing it (by answering or pressing Escape) ends the question entirely, which breaks the flow.

Proposed Solution

Add a collapse/minimize toggle to the AskUserQuestion widget so users can temporarily hide it, scroll up to review earlier output, and expand it again to respond — without losing their place in the flow.

A small ▾ / ▸ arrow on the widget header collapses it to a single title bar
The widget remembers its state and re-expands when the user clicks it
Alternatively, a "Show later" option dismisses the widget temporarily and re-surfaces it when the user next sends a message

Alternative Solutions

Currently there is no workaround. Pressing Escape cancels the question entirely rather than deferring it. Scrolling up while the widget is visible is possible but the widget still occupies a large portion of the screen making it hard to read context. Other terminal-based interactive UIs (e.g. fzf, gum) handle this by rendering inline and restoring the scroll position after selection.

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

1. I run /create-urlContentElement, a custom CRUD skill for managing authoring content elements
2. The skill lists existing records in a formatted table in the chat
3. Immediately after, an AskUserQuestion widget appears asking "What would you like to do?"
4. The widget covers the table I just need to reference to make my choice
5. With a collapse toggle, I could hide the widget, scroll up to check the table, then expand and answer — without cancelling the question or restarting the flow

Additional Context

This particularly affects multi-step skills (.claude/skills/) that alternate between displaying data and asking for user input. The pattern of "show results → ask next action" is very common in interactive skill flows, and the current widget behavior makes it feel like the UI is fighting the user instead of supporting them.