to-questionnaire
The facts
Its description
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
The description the agent reads to decide when to use it.
When it starts
This skill is not picked by the agent from its name and description: its frontmatter sets disable-model-invocation, so it is loaded only when the user invokes it directly, for example as a slash command. It is for turning a decision the user cannot answer alone into a questionnaire that someone else fills in.
A model's summary of when it is used.
Who can start it
Only you
Only you can start it. The agent never picks it on its own.
What leads to it
- ask-matt hands off to this when the blocker is in someone else's head ask-matt, line 89
Other skills that hand off to this one, call it, require it or offer it instead, as a model read them.
Licence
MIT, from LICENSE
The terms its author shares it under, which let it be shown here.
Other files in this skill (1) Close
The text
Most marks come from matching words in the file, so treat them as pointers.
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.
- 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, since 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.
<questionnaire-template>
<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>
Raw lines 18 to 29Context
One paragraph orienting a recipient who wasn't in the user's head. Enough to answer well, not a page.
Raw lines 30 to 33How 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.
Raw lines 34 to 37<Theme heading>
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.
<question-example>
Raw lines 38 to 42What load is the system expected to handle at launch?
Why this matters: it decides whether we provision for burst traffic now or defer it.
</question-example>
Raw lines 43 to 49From mattpocock/skills at 4ae2317, 2026-10-31. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.