To questionnaire
Turn something the user can't answer alone into a questionnaire: a Markdown document they hand to one person to fill in async, or work through together in 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.
Steps
Who is it going to? In one exchange through your harness's question tool (with none, ask in plain text and end the turn), get the recipient's role, expertise, and relationship to the user. This fixes the tone and how much context the document must carry. Done when you know who the recipient is and what they know that the user doesn't. Skip any step the conversation already answers.
What do you need back? In one question-tool exchange, get the specific decisions or facts the user can't resolve alone and needs from this person. If the user can't name them, propose a list from context and confirm it. 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>.md(slug from the topic) outside the repo (the OS temp directory), or ask where; never into the current directory when that is a repo. 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, since async means you may only get one pass. Group them under ## headings by theme once there are more than a handful.
# <Questionnaire title>
**Purpose:** why this questionnaire exists and the decision riding on it.
**From:** <the user>, **To:** <the recipient>, **How your answers will be used:** <where they go>
## 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.
## <Theme heading>
### <One question, one idea>
_Why this matters: <one line, only where the question could be misread or invite a throwaway answer.>_
>
## Anything else?
A closing catch-all: anything we didn't ask that we should know?
Every question is one idea, never compound, with an empty > line beneath it for the answer. A question whose answer you could get by running code or reading a file does not belong here — that is your job, not the recipient's.