AutoGineer
Generated banner for To Questionnaire
Generated logo for To Questionnaire

To Questionnaire

Matt PocockCommunityCreated by Matt Pocock

  • Skill
  • Content generator
  • Business and productivity
  • MIT
  • No issues found
Download ZIP

From the author

Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
— the description by Matt Pocock

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill helps users bridge knowledge gaps by generating structured Markdown questionnaires. It guides the user through identifying the recipient's expertise and the specific information required, then produces a formatted document designed for asynchronous or meeting-based information gathering.

What it does

  • Identifies the recipient's role and relationship to the user to set the appropriate tone.
  • Extracts a list of specific decisions or facts the user needs to resolve.
  • Drafts a discovery questionnaire in Markdown format.
  • Structures questions by theme with clear purpose statements.
  • Saves the final questionnaire as a Markdown file in the current directory.

When to use it

  • When you need to make a decision but lack the necessary information.
  • When you need to extract specific technical or business context from a colleague.
  • When preparing for an interview or meeting where you need to gather structured input.
  • When you need to request information asynchronously and want to ensure the recipient understands the context.

Advantages

  • Ensures questions are targeted at the specific knowledge gap.
  • Provides a consistent template for professional information requests.
  • Reduces ambiguity by requiring clear purpose statements for questions.
  • Facilitates better responses by providing context to the recipient.

Usage examples

“I need to decide on a cloud provider but don't know our security requirements. Create a questionnaire for our CISO.”
The agent will ask about the CISO's role and the specific security decisions needed, then generate a Markdown file containing a structured questionnaire for the CISO to complete.
“I need to finalize the project scope but the client hasn't provided the budget constraints. Help me ask them.”
The agent will guide you through defining the project context and the specific budget information required, resulting in a formal questionnaire document.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/mattpocock/to-questionnaire/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip to-questionnaire.zip -d .agents/skills

Documentation by Matt Pocock

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.

  1. 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.

  2. 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.

  3. 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 in 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>

Files

LICENSE

MIT License

Copyright (c) 2026 Matt Pocock

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Requirements and compatibility

Written for: Claude Code

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Claude Code frontmatter

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Matt Pocock
Publisher
Matt Pocock (Community)
Source
mattpocock/skills · skills/productivity/to-questionnaire · commit 4ae2317
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Matt Pocock or Matt Pocock.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download to-questionnaire.zip