to-questionnaire

Generates a Markdown discovery questionnaire for a recipient who holds knowledge the user lacks.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/MSC72m/DevForge --skill to-questionnaire-msc72m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-questionnaire
Source: https://github.com/MSC72m/DevForge/tree/main/skills/to-questionnaire
Command: npx skills add https://github.com/MSC72m/DevForge --skill to-questionnaire-msc72m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a decision depends on information only someone else has, ad-hoc messages and meetings waste the one async pass you may get. This Skill turns an unanswerable decision into a structured questionnaire document that pulls the needed knowledge out of the right person. ## Core Features & Use Cases - Recipient Targeting: Interviews the user about who the questionnaire goes to, fixing tone and how much context the document must carry. - Gap-Focused Questions: Drafts questions aimed at the gap between what the recipient knows and what the user needs, ordered most-important-first. - Structured Markdown Output: Writes a themed questionnaire with answer stubs and a catch-all section to to-questionnaire-<slug>.md in the current directory. - Use Case: A product manager unsure about infrastructure requirements drafts a questionnaire for the ops lead, covering expected launch load, scaling constraints, and budget, then sends it for async completion. ## Quick Start Ask the assistant to turn the decision you cannot answer alone into a questionnaire for the person who holds the missing knowledge.

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 back from them. The Skill drafts a Markdown questionnaire targeting that knowledge gap and writes it to a file you can send for async completion.

What makes a good discovery questionnaire for async answers?▼

Order questions most-important-first since you may only get one pass, keep each question to a single idea, and group them under themed headings. Include answer stubs and a closing catch-all for anything not asked.

Can I use this for stakeholder requirements gathering?▼

Yes, requirements gathering is a core scenario. The questionnaire frames the decision riding on the answers, orients the recipient with brief context, and extracts the specific facts you cannot resolve alone.

Where is the generated questionnaire file saved?▼

The questionnaire is written to the current directory as to-questionnaire-<slug>.md, where the slug derives from the topic. The Skill reports the file path after writing it.

When should I use a questionnaire instead of a meeting?▼

Use it when the recipient holds knowledge you lack and async communication may allow only one pass. It also works as preparation for a live meeting, where both parties fill it out together.