to-questionnaire

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

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Kaleb-Rupe/aurora --skill to-questionnaire-kaleb-rupe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-questionnaire
Source: https://github.com/Kaleb-Rupe/aurora/tree/main/claude/skills/to-questionnaire
Command: npx skills add https://github.com/Kaleb-Rupe/aurora --skill to-questionnaire-kaleb-rupe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a decision depends on knowledge held by someone else, ad-hoc conversations waste time and miss key questions. This Skill turns an unanswerable decision into a structured Markdown questionnaire that one person can fill in asynchronously or together in a meeting. ## Core Features & Use Cases - Recipient Profiling: Identifies who the questionnaire goes to, their expertise, and their relationship to the user to set tone and context depth. - Gap-Targeted Questions: Drafts questions aimed at the gap between what the recipient knows and what the user needs, ordered most-important-first. - Structured Document Template: Produces a discovery questionnaire with purpose, context, answer instructions, themed sections, answer stubs, and a catch-all closing section. - Use Case: A product manager needs infrastructure details from a senior engineer before planning a launch. The Skill interviews the manager about the recipient and needed answers, then writes a ready-to-send questionnaire file. ## Quick Start Ask the assistant to turn a decision you cannot 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 a colleague to answer asynchronously?

Describe who the questionnaire goes to and what answers you need back. The Skill drafts a Markdown document with themed, most-important-first questions and answer stubs, saved as a to-questionnaire-<slug>.md file you can send directly.

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 include a short context section so the recipient can answer well. Partial answers and explicit uncertainty flags are encouraged over skipped questions.

Can I use a questionnaire instead of a live meeting?

Yes, the generated document works for both async handoff and live fill-in during a meeting. The structure includes a purpose statement, context paragraph, and answer instructions so the recipient can respond without a real-time conversation.

When should I not use a written questionnaire?

Avoid it when the topic requires rapid back-and-forth probing, negotiation, or reading emotional cues, since async documents allow only one pass. It also fits poorly when the recipient's knowledge is unclear and questions cannot be targeted at a known gap.

What format does the questionnaire output use?

The output is a Markdown file named to-questionnaire-<slug>.md in the current directory. It contains a title, purpose line, context section, answer instructions, themed question sections with answer stubs, and a closing catch-all question.