native-question-uxlisted

## Activation Contract Load when another skill delegates question presentation. This skill changes only HOW questions are shown, never their semantics, wording, or order. The delegating flow owns what to ask; this owns how it appears. ## Hard Rules - Use a runtime's native question UX only when that mechanism is explicitly available in the current runtime/session. - Never invent or assume a tool, prompt primitive, or UI capability that is not explicitly available. - Preserve the delegating flow's semantics: ask one question at a time, keep open-ended questions open-ended, and stop/wait after each answer. - Reserve the native question UX for genuinely discrete, bounded-option decisions: gates, grades, confirmations, and mode choices. - Open-ended questions — where the delegating flow expects a free-text answer (interview questions, Socratic debriefs, teach-back prompts) — are always asked in normal chat, even when the native mechanism offers a custom/freeform answer field. - For bounded questions, when the native mechanism presents selectable options, put the delegated recommendation first/recommended; rely on any built-in custom/freeform answer field instead of adding a separate selectable custom/chat option; in opencode, rely on the built-in `Type your own answer` path. - If no suitable native mechanism is explicitly available, ask in normal chat. - Claude Code `AskUserQuestion` and opencode `question` are examples only; never treat either as required. ## Decision Gates