Skill

survey-design

Designs rigorous customer survey instruments with objective setting, audience sampling, question logic, branching flows, and QA checklists. Useful for launching surveys or improving response quality.

design

From customer-feedback-orchestration

Install

Run in your terminal

npx claudepluginhub gtmagents/gtm-agents --plugin customer-feedback-orchestration

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

executing-plans

Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.

superpowers

134.2k

finishing-a-development-branch

Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.

superpowers

134.2k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

134.2k

Stats

Parent Repo Stars138

Parent Repo Forks24

Last CommitNov 19, 2025

Actions

View Source View Plugin View on GitHub View README

Customer Survey Design Kit Skill

When to Use

Launching new surveys or refreshing existing templates.
Diagnosing low response quality or bias in ongoing programs.
Training GTM teams on survey best practices.

Framework

Objective Clarity – define single-topic goals, hypotheses, and decision criteria.
Audience & Sampling – specify personas, quotas, suppression rules, and incentive plan.
Question Architecture – balance quant vs qual questions, avoid double-barreled prompts, include screener + validation items.
Logic & Branching – outline conditional flows, progress indicators, and completion time targets.
QA Checklist – test across devices, languages, anonymity rules, and data export formats.

Templates

Survey brief (goal, audience, sample, success metrics).
Question bank categorized by objective (adoption, satisfaction, pricing, roadmap).
QA script for reviewers to confirm copy, logic, and translations.

Tips

Cap surveys at <10 minutes unless offering significant incentives.
Randomize answer choices when appropriate to reduce bias.
Pair with stakeholder-ops to align approvals and launch windows.