Decision questionnaire
Writes a Markdown questionnaire for someone who holds knowledge the user lacks, after asking only who it goes to and what answers are needed, with the most important questions first. Use when a decision depends on facts from another person.
to-questionnaire- Author
- Matt Pocock
- Source
- mattpocock/skills/skills/productivity/to-questionnaire @ abeeaf9
- License
- MIT · Copyright (c) 2026 Matt Pocock
About this skill
What it does
The skill is for a decision that depends on knowledge you do not have. The agent questions you only about the send, which you can always answer: in one exchange, who the questionnaire goes to (role, expertise, relationship to you); in a second, which decisions or facts you need back. Then it aims questions at the gap and saves them to to-questionnaire-<slug>.md in the current folder. It is done only when every item you named has a question.
The document follows a fixed template: purpose and the decision riding on it, sender, recipient and how answers will be used, one paragraph of context, "How to answer" with deadline and effort, themed ## sections with the most important questions first, and a closing "Anything else?". Each question holds one idea, with an empty quote line for the answer, and gets a one-line "why this matters" only where it could be misread. The file works sent ahead or filled in together on a call.
The skill is SKILL.md alone; agents/openai.yaml sets the Codex name and turns off implicit invocation.
When to use it, and when not
Use it when you need answers from a client, an expert, another team or a manager before deciding: expected load, business rules, how a legacy system behaves.
Skip it when you hold the answers yourself, or when a couple of questions fit in one chat message.
How to run it
The install command below puts the whole folder in place. The skill has disable-model-invocation: true, so the agent never starts it on its own: it runs only when you call it.
- Claude Code: only the
/to-questionnairecommand — naming the skill in a message will not start it. - Codex:
$to-questionnaire. - Cursor: type
/in the Agent chat and pickto-questionnaire.
Example: /to-questionnaire We must decide whether to keep the old billing service or rewrite it, and only the ops lead knows how it works.
How it differs from similar skills
Grilling a plan by the same author questions you live, round by round, until every decision is settled. This skill grills you only on the recipient and the answers you need, and moves the subject questions into a document for someone else. Interview me asks you one question at a time to find what you actually want. No other skill in the catalog writes questions for a third person to answer.
Install
Run one command — it saves SKILL.md and the files it uses into your agent's skills folder. Claude Code and Codex pick up a new skill without a restart; if it does not show up, restart the agent.
curl -fsSL --create-dirs -o ~/.claude/skills/to-questionnaire/SKILL.md https://anymodel.org/en/skills/matt-pocock/to-questionnaire/SKILL.md -o ~/.claude/skills/to-questionnaire/LICENSE https://anymodel.org/en/skills/matt-pocock/to-questionnaire/LICENSE -o ~/.claude/skills/to-questionnaire/agents/openai.yaml https://anymodel.org/en/skills/matt-pocock/to-questionnaire/agents/openai.yaml
curl -fsSL --create-dirs -o ~/.agents/skills/to-questionnaire/SKILL.md https://anymodel.org/en/skills/matt-pocock/to-questionnaire/SKILL.md -o ~/.agents/skills/to-questionnaire/LICENSE https://anymodel.org/en/skills/matt-pocock/to-questionnaire/LICENSE -o ~/.agents/skills/to-questionnaire/agents/openai.yaml https://anymodel.org/en/skills/matt-pocock/to-questionnaire/agents/openai.yaml
foreach ($f in 'SKILL.md','LICENSE','agents/openai.yaml') { $p = Join-Path "$HOME\.claude\skills\to-questionnaire" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/matt-pocock/to-questionnaire/$f" -UseBasicParsing -OutFile $p }foreach ($f in 'SKILL.md','LICENSE','agents/openai.yaml') { $p = Join-Path "$HOME\.agents\skills\to-questionnaire" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/matt-pocock/to-questionnaire/$f" -UseBasicParsing -OutFile $p }Any other agent: save the file into its skills folder, or give it the link to the file: https://anymodel.org/en/skills/matt-pocock/to-questionnaire/SKILL.md
SKILL.md
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>
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 ## 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>
What 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>
Anything else?
A closing catch-all: anything we didn't ask that we should know?
</questionnaire-template>
Connect through AnyModel API
This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.
AnyModel