--- name: to-questionnaire description: Draft a questionnaire for another person or group to supply missing facts or decisions, asynchronously or in a meeting; not a live interview with the user. --- Turn something the user cannot answer alone into a **questionnaire**: a document they can hand to someone who holds the missing knowledge or decision. Aim at the **gap** between what that recipient knows and what the user needs back. **Grill the send, not the subject.** Establish who it goes to and what the answers must enable. Use what the user already supplied; ask only for missing recipient context or purpose that would materially change the questions, or draft with labeled assumptions when the user wants a draft now. The user need not answer the very questions they are asking you to prepare. - **Who is it going to?** Identify the recipient's role, relevant knowledge and relationship to the user so tone and context fit them. With several recipients, make each person's questions clear rather than assuming everyone knows or decides the same things. - **What do you need back?** Identify the facts or decisions the user must walk away able to act on. Distinguish recipient decisions from requests for advice. Use known answers as context; keep assumptions visibly provisional. - **Write the questionnaire.** Cover every item the user needs back and any other material gap with a question the intended recipient can answer. Put the important questions first and prerequisites before dependent questions. Express a dependency simply, such as “If yes, …”. Give the recipient enough context to answer without this conversation: an asynchronous questionnaire may get only one pass. Include only material appropriate for that recipient; omit unrelated or restricted internal details. Flag any question that cannot be answered with shareable context, and continue drafting the rest. Keep questions neutral, one idea at a time. Where options help, allow an unlisted answer, uncertainty or a conditional answer. Do not smuggle a preferred decision into the question or supply answers on the recipient's behalf. ## Document shape Adapt the shape to the user's requested format. A short questionnaire can be a short list; use theme headings when they help. - **Purpose:** the decision or action the answers will support. - **Context:** the relevant facts and labeled assumptions, briefly. - **How to answer:** the supplied deadline or effort expectation, if any. Partial answers and “I don't know” are useful; invite the recipient to distinguish facts from estimates. - **Questions:** important first, grouped where useful, with room for answers in a document. Add a brief reason only where a question could be misunderstood or receive an unhelpful answer. - **Anything else?** Invite missing context that could change the decision. Return the draft in the requested place and format; without a requested destination, return it in the response. If the user wants a saved Markdown file and no location is established, use `to-questionnaire-.md` in the working directory and report its path. Drafting does not itself authorize sending the questionnaire or collecting responses.