Turn something the user can't answer alone into a questionnaire — a Markdown document they hand to one person to fill in async, or fill out together over a meeting. The recipient holds knowledge the user lacks; the questionnaire pulls it out of them.
Grill the send, not the subject. Interview the user only about the send, which they can always answer: who it goes to, and what they need back. The questions in the document then target the gap between what the recipient knows and what the user needs. Route the setup questions through AskUserQuestion (Claude Code) or request_user_input (Codex) when available — the full question protocol lives in grill-me-plus.
-
Who is it going to? Ask, in one exchange, the recipient's role, expertise, and relationship to the user. This fixes the questionnaire's tone and how much context it must carry. Done when you know who the recipient is and what they know that the user doesn't.
-
What do you need back? Ask, in one exchange, the specific decisions or facts the user can't resolve alone and needs from this person. Done when you have a concrete list of what the user must walk away able to do or decide.
-
Write the questionnaire. Draft questions aimed at the gap from steps 1–2, following the Document structure below. Write it to
to-questionnaire-<slug>.mdin the current directory (slug from the topic) and report the path. Done when the file exists and every item the user named in step 2 is covered by a question.
Document structure
Frame the document as a discovery questionnaire: the user lacks context, the recipient holds it. Order questions most-important-first — async means you may only get one pass — and group them under ## headings by theme once there are more than a handful. Write it using the template below.
Purpose: why this questionnaire exists and the decision riding on it.
From: — To: — How your answers will be used:
Context
One paragraph orienting a recipient who wasn't in the user's head. Enough to answer well, not a page.
How to answer
Deadline and rough effort. Partial answers and "I don't know" are useful — flag anything you're unsure of rather than skipping it.
One ## section per theme. Under each, its questions, most-important-first. Every question is one idea — never compound — with an answer stub directly beneath, and a one-line why this matters only where the question could be misread or invite a throwaway answer.
Why this matters: it decides whether we provision for burst traffic now or defer it.
Anything else?
A closing catch-all: anything we didn't ask that we should know?
When you're done
End the session by printing the block below — on a clean finish, a stop, or a dead end. On harnesses without slash commands, write the command as plain phrasing (run grill-me-plus on <ref>) instead of /grill-me-plus <ref>.
---
Pipeline: **decide** → spec → slice → build (questionnaire feeds decide)
Done: <file path; who it's for; what it needs back>
Next:
• <condition> → /<skill> <ref>
List only the conditions that actually apply, most likely first:
- Questionnaire written, answers not back yet → nothing to run; send it, then
/grill-me-pluson the blocked branch once answers land. Name the branch so the next session knows what was waiting. - Answers already in hand →
/grill-me-pluson the blocked branch, feeding the answers in - It unblocks a
wayfinder-plusticket →/wayfinder-plus <map>once answered; note the ticket stays open until then - Part of the gap is a documented fact, not a person's knowledge →
/research-pluson that part in parallel - Stopped before finishing → say what the draft covers and which of the user's needs have no question yet