to-questionnaire

Generates a structured Markdown questionnaire to extract knowledge from a specific recipient.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/toderian/project_template --skill to-questionnaire-toderian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-questionnaire
Source: https://github.com/toderian/project_template/tree/main/plugins/agents-extras/skills/to-questionnaire
Command: npx skills add https://github.com/toderian/project_template --skill to-questionnaire-toderian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you cannot answer a decision alone, this Skill turns that gap into a written questionnaire you hand to the one person who holds the missing knowledge, so answers come back async or in a single meeting. ## Core Features & Use Cases - Recipient Targeting: Interviews you only about who the questionnaire goes to and what you need back, fixing tone and context level. - Structured Document: Produces a Markdown questionnaire with purpose, context, answer instructions, themed question sections ordered most-important-first, and a catch-all closing section. - Inbox Integration: Saves the file to docs/resources/_inbox/ when that directory exists so answered copies feed downstream knowledge distillation. - Use Case: You are blocked on infrastructure decisions before launch. The Skill drafts a questionnaire for your DevOps lead covering expected load, scaling constraints, and provisioning trade-offs, ready to send async. ## Quick Start Ask the assistant to turn the decision you are stuck on into a questionnaire for the person who can answer it.

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 to get answers from a colleague?▼

Describe who the recipient is and what decisions or facts you need back. The Skill drafts a Markdown questionnaire with themed sections ordered most-important-first, answer stubs under each question, and a closing catch-all, then saves it to a file.

What format does the generated questionnaire use?▼

The output is a Markdown document with a purpose statement, a short context paragraph, answer instructions with deadline and effort expectations, one section per theme, and an 'Anything else?' closing section for missed topics.

Where is the questionnaire file saved?▼

It saves to docs/resources/_inbox/<date>-questionnaire-<slug>.md when that directory exists, so answered copies feed downstream knowledge distillation. Otherwise it writes to-questionnaire-<slug>.md in the current directory.

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

Use it when the recipient holds knowledge you lack and async answers are acceptable, since questions are ordered most-important-first in case you get only one pass. It also works as an agenda worked through together live.

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

Only two things: who the recipient is (role, expertise, relationship to you) and the specific decisions or facts you cannot resolve alone. The Skill never interviews you about the subject matter itself.