to-questionnaire

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

Updated Apr 16, 2025
One-click install
npx skills add https://github.com/damoke012/eks_code --skill to-questionnaire-damoke012
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-questionnaire
Source: https://github.com/damoke012/eks_code/tree/main/.claude-env/skills/to-questionnaire
Command: npx skills add https://github.com/damoke012/eks_code --skill to-questionnaire-damoke012

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. ## Core Features & Use Cases - Recipient scoping: Identifies who the questionnaire goes to, their expertise, and their relationship to you, fixing tone and context level. - Gap-targeted questions: Drafts questions aimed at the specific decisions or facts you cannot resolve alone, ordered most-important-first. - Structured Markdown output: Writes a discovery questionnaire with purpose, context, themed sections, answer stubs, and a catch-all closing section to a to-questionnaire-<slug>.md file. - Use Case: You need infrastructure capacity numbers from an ops engineer before planning a launch. The Skill interviews you about the recipient and what you need back, then produces a ready-to-send questionnaire covering every open item. ## Quick Start Ask the assistant to turn the decision you can't 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 with themed sections, ordered most-important-first, and writes it to a to-questionnaire-<slug>.md file you can send.

What should a discovery questionnaire include?▼

A discovery questionnaire should include a purpose statement, a short context paragraph, answer instructions with a deadline, themed question sections with answer stubs, and a closing catch-all. Questions should each cover one idea and be ordered by importance.

Can I use a questionnaire for async stakeholder input?▼

Yes, the questionnaire is designed for asynchronous use where you may only get one pass at answers. Questions are ordered most-important-first and partial or uncertain answers are explicitly welcomed rather than skipped.

When should I not use a written questionnaire?▼

Avoid a questionnaire when the topic requires live back-and-forth probing, when the recipient's answers will raise immediate follow-ups, or when the knowledge gap is small enough to resolve in a quick direct conversation.