# Question Tools for Matt Pocock Grilling Flows Scope: apply only while running Matt Pocock's grilling flows (grill-me, grilling, grill-with-docs, loop-me, or a skill explicitly delegating its interview to one of these). This changes question delivery, not the flow's research, decision criteria, documentation, or completion requirements. Ordinary coding conversations and unrelated skills keep their own behavior. 1. Research what the codebase can answer before asking the user. The main conversation agent owns the interview; subagents return findings and proposed questions to it rather than independently prompting the user. 2. Use the host's native interactive question tool when exposed and permitted in the current session: Claude Code `AskUserQuestion`, Codex `request_user_input`, or OpenCode `question`. Follow its actual schema and mode/permission restrictions. Do not invent a tool, change modes merely to unlock one, or bypass a restriction. In Codex, `request_user_input` may be limited to Plan mode; use the fallback when it is unavailable. 3. Preserve the originating flow's round size and pacing. If it calls for one question at a time, ask one. If it allows a round of independent questions, batch only those that can be answered without knowing another answer. Wait for each answer before formulating dependent follow-ups. Split rounds across sequential tool calls when question, option, or text limits require it; retain every decision rather than silently dropping questions. 4. Give enough context to decide, concrete options with tradeoffs, and your recommendation with a short reason when you have one. Mark the recommended option clearly. Keep choices neutral enough to disagree with; never invent a recommendation just to fill the UI. Put context outside the tool if its field limits would lose necessary detail. 5. Preserve custom responses: use the tool's built-in free-text/Other facility where available. If it cannot accept a needed custom answer, invite a plain text reply instead. Do not force an open-ended question into false choices or interpret Other as agreement with a listed option. 6. Treat skipped, dismissed, empty, or ambiguous answers as unresolved, not consent and not acceptance of the recommendation. Clarify a blocking gap or explicitly defer it with the user's agreement. Track unresolved decisions and keep them out of the confirmed decisions in any spec, ADR, or summary. 7. If the native tool is absent, disallowed, fails, or cannot express the question faithfully, ask in plain text and wait. Use the same round rules, numbered questions/options, recommendation and reason, and an explicit invitation to give a custom answer. Resume the native tool when usable. This is an instruction preference, not runtime enforcement. Higher-priority instructions and host restrictions still apply. Finish only when the original flow's completion criteria are met; changing the UI does not satisfy them.