questionnaire-design

Design requirements questionnaires with structured question types, scales, and bias-resistant ordering.

23|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/jdm4pku/RE-Skills --skill questionnaire-design-jdm4pku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: questionnaire-design
Source: https://github.com/jdm4pku/RE-Skills/tree/main/skills/questionnaire-design
Command: npx skills add https://github.com/jdm4pku/RE-Skills --skill questionnaire-design-jdm4pku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Gathering requirements input from large stakeholder groups is impractical through one-on-one interviews, and poorly designed surveys produce biased, uninterpretable data. This Skill guides the design of requirements questionnaires that validate and prioritize findings across broad audiences with quantitative rigor. ## Core Features & Use Cases - Question Type Selection: Covers open vs. closed questions, Likert scales, ranking, and forced-choice formats with guidance on when each applies. - Bias-Resistant Design: Provides ordering rules, balanced scale construction, and checklists to eliminate leading, double-barreled, and loaded questions. - Deployment and Analysis Guidance: Includes distribution strategies by audience size, response rate targets, pilot testing steps, and result analysis with cross-tabulation by user class. - Use Case: After interviewing 5 stakeholders, you need to validate feature priorities across 200 lab users. Use this Skill to build a 12-question questionnaire, deploy it, and convert ranking results into Release 1 scope decisions. ## Quick Start Design a requirements questionnaire to validate feature priorities with all 200 users across our 8 labs, using ranking and Likert scale questions.

Frequently Asked Questions about questionnaire-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a requirements gathering questionnaire?▼

Start by defining the decision the data will inform, then draft questions using closed formats like Likert scales, ranking, and forced choice. Order questions from factual to opinion-based, pilot test with 3-5 people, and keep the total under 15-20 questions.

Should I use a questionnaire or interviews for requirements elicitation?▼

Use interviews first to discover requirements through open-ended exploration, then use questionnaires to validate and prioritize findings with larger groups. Questionnaires confirm what you already know; they do not discover new requirements.

What question types work best in requirements surveys?▼

Likert scales measure satisfaction and agreement, ranking questions reveal feature priorities, and forced-choice questions expose real tradeoffs. Limit open-ended questions to 1-3 per questionnaire since they are hard to analyze at scale.

How many questions should a requirements questionnaire have?▼

Keep questionnaires to 15-20 questions with completion time under 10 minutes. Completion rates drop roughly 20% for every 5 questions beyond 15, and every question should map to a specific decision it informs.

Why do questionnaire results get biased and how do I prevent it?▼

Bias comes from leading questions, double-barreled questions, unbalanced scales, and non-response patterns. Use balanced positive and negative scale options, one concept per question, neutral wording, and track response rates by stakeholder group.

When should I not use a questionnaire for requirements gathering?▼

Avoid questionnaires as the first elicitation activity or when you need deep exploratory discovery. They produce shallow, predefined responses without follow-up capability, so use interviews or observation when requirements are still unknown.