to-questionnaire

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

Updated May 9, 2024
One-click install
npx skills add https://github.com/AceCodePt/dotfiles --skill to-questionnaire-acecodept
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-questionnaire
Source: https://github.com/AceCodePt/dotfiles/tree/main/.config/opencode/flows/to-questionnaire
Command: npx skills add https://github.com/AceCodePt/dotfiles --skill to-questionnaire-acecodept

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you can't answer a decision yourself, you need input from someone else — but ad-hoc messages waste their time and miss key questions. This Skill turns that gap into a structured Markdown questionnaire the recipient can fill in asynchronously or during a meeting. ## 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 knowledge gap between what the recipient knows and what you need to decide. - Structured document output: Writes a discovery questionnaire to to-questionnaire-<slug>.md with purpose, context, themed sections ordered most-important-first, and answer stubs. - Use Case: You need infrastructure decisions from a senior engineer before launch. The Skill interviews you about what you need back, then produces a questionnaire covering load expectations, scaling, and provisioning that the engineer answers async. ## Quick Start Ask the assistant to turn the decision you're stuck on into a questionnaire for the person who has the answers, naming who they are and what you need back.

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?▼

State 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, answer stubs, and a closing catch-all, saved as to-questionnaire-<slug>.md.

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 context so the recipient can answer well without a meeting.

Can the questionnaire be filled out during a live meeting?▼

Yes. The document works both as an async hand-off and as a shared agenda filled in together during a meeting. The structure and answer stubs support either mode without changes.

When should I not use a written questionnaire?▼

Avoid it when the knowledge gap requires interactive back-and-forth, whiteboarding, or probing follow-ups that a static document cannot support. In those cases a live interview or workshop fits better than an async form.