to-questionnaire

Generates a structured Markdown questionnaire for a recipient to answer asynchronously.

Updated Feb 22, 2024
One-click install
npx skills add https://github.com/tlipoca9/dotfiles --skill to-questionnaire-tlipoca9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-questionnaire
Source: https://github.com/tlipoca9/dotfiles/tree/main/home/dot_agents/skills/to-questionnaire
Command: npx skills add https://github.com/tlipoca9/dotfiles --skill to-questionnaire-tlipoca9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you can't answer a decision alone, you need input from someone who holds the missing knowledge. This Skill turns that gap into a written questionnaire the recipient can fill in asynchronously or together in a meeting, so you get usable answers in one pass instead of scattered back-and-forth. ## Core Features & Use Cases - Recipient profiling: Identifies who the questionnaire goes to, their expertise, and their relationship to you, fixing tone and context level. - Gap-targeted questions: Drafts questions aimed precisely at the decisions or facts you cannot resolve alone, ordered most-important-first. - Structured Markdown output: Writes a ready-to-send document with purpose, context, answer instructions, themed sections, and answer stubs to to-questionnaire-<slug>.md. - Use Case: You need infrastructure capacity numbers from an ops engineer before launch. The Skill interviews you about the recipient and what you need back, then produces a discovery questionnaire with questions like expected launch load, each with a why-it-matters note and an answer stub. ## Quick Start Ask the assistant to turn a decision you can't answer alone into a questionnaire for a specific colleague to fill in.

Frequently Asked Questions about to-questionnaire

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a questionnaire for someone else to fill in?▼

Describe who the recipient is and what decisions or facts you need from them. The Skill drafts a Markdown questionnaire with themed sections, one idea per question, and answer stubs, then saves it as to-questionnaire-<slug>.md in the current directory.

What makes a good async discovery questionnaire?▼

Order questions most-important-first since you may only get one pass, keep each question to a single idea, and add a one-line why-this-matters note where a question could be misread. Include a closing catch-all for anything not asked.

Can I use this for live meetings instead of async surveys?▼

Yes. The generated document works both as an async form the recipient fills in alone and as an agenda you fill out together during a meeting. The structure and question ordering stay the same.

What information do I need to provide before the questionnaire is written?▼

Two things: the recipient's role, expertise, and relationship to you, and the specific decisions or facts you cannot resolve alone. The Skill asks about these in two short exchanges before drafting.

When should I not use a written questionnaire?▼

Avoid it when the knowledge gap requires interactive probing, negotiation, or sensitive discussion where tone matters. A questionnaire suits extracting facts and decisions, not resolving conflicts or exploring ambiguous topics together.