to-questionnaire

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

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/j172/bid --skill to-questionnaire-j172
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-questionnaire
Source: https://github.com/j172/bid/tree/main/agent/skills/to-questionnaire
Command: npx skills add https://github.com/j172/bid --skill to-questionnaire-j172

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 recipient can fill in asynchronously or during a meeting. ## Core Features & Use Cases - Recipient Scoping: Interviews the user about who the questionnaire goes to, fixing tone and required context. - Gap-Targeted Questions: Identifies exactly what the user needs back and drafts questions aimed at the knowledge gap. - Structured Document Output: Writes a discovery questionnaire to to-questionnaire-<slug>.md with purpose, context, themed question sections ordered most-important-first, answer stubs, and a catch-all closing section. - Use Case: A product manager needs infrastructure constraints from an ops engineer before planning a launch. The Skill produces a questionnaire covering load expectations, deadlines, and open risks that the engineer answers async. ## Quick Start Ask the assistant to turn a 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 to answer asynchronously?

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 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, sender and recipient, a short context paragraph, answer instructions with deadline, themed question sections with answer stubs, and a closing catch-all for anything not asked.

Can the questionnaire be filled out during a live meeting?

Yes. The generated Markdown document works both as an async form one person fills in and as an agenda for filling out together over a meeting, since questions are grouped by theme and ordered by importance.

When should I not use a written questionnaire?

Avoid it when the knowledge gap requires interactive back-and-forth probing, when the recipient cannot write answers, or when the decision is trivial enough to resolve in a single direct message.

Where is the generated questionnaire file saved?

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