Skip to main content
command CX Codex

run-survey — Claude Code command: what it does, how to install

run-survey orchestrates customer surveys with target sampling, structured question banks, and distribution steps.

Apache-2.0 ★ 450 updated 2026-04-03

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/run-survey.md
Open on GitHub

What run-survey does

This command sets up end-to-end customer surveys across specific segments. It structures the initial brief, constructs questions with branching logic, manages distribution lists, and tracks fielding progress.

The process logs plan schemas into .claude/plans/plan-<timestamp>.json with clear dependency trees and error handling. It coordinates specialized agents like research-lead and cs-analyst, enforcing a default retry limit of 2 for delivery failures before triggering escalations.

What it helps with

  • orchestrate targeted user research surveys with specific goals
  • generate branching question banks with recommended scales
  • build distribution plans across email, in-app, or CS channels
  • record execution blueprints in plan JSON files for auditing

Example prompts for the agent

  • /customer-feedback-orchestration:run-survey --audience "admins" --goal adoption --channels "email,in-app" --deadline 2025-12-15
  • /customer-feedback-orchestration:run-survey --audience "champions" --goal satisfaction --channels "community" --sample_size 150
  • /customer-feedback-orchestration:run-survey --audience "exec sponsors" --goal "roadmap validation" --channels "CS-led" --deadline 2026-01-30

How to install run-survey

Manually: put the files in place

.claude/commands/run-survey.md

Call it with /run-survey. For all projects use ~/.claude/commands/

Questions about run-survey

How to install run-survey in Claude Code?

Place the command specification file at .claude/commands/run-survey.md.

What does run-survey do?

It manages survey preparation from brief assembly and question design to sampling, tracking, and handoff to feedback synthesis.

Which parameters are supported by run-survey?

It accepts audience, goal, channels, and deadline, alongside optional sample_size and incentive options.

Source text

run-survey.md · Apache-2.0
---
name: run-survey
description: Launches customer surveys with sampling plans, question sets, and automation hooks.
usage: /customer-feedback-orchestration:run-survey --audience "admins" --goal adoption --channels "email,in-app" --deadline 2025-12-15
---

# Command: run-survey

## Inputs
- **audience** – persona or segment target (admins, champions, exec sponsors).
- **goal** – objective (adoption, roadmap validation, satisfaction, messaging test).
- **channels** – comma-separated distribution methods (email, in-app, community, CS-led).
- **deadline** – fielding end date or fixed duration.
- **incentive** – optional reward description or budget.
- **sample_size** – desired number of responses (numeric).

### GTM Agents Pattern & Plan Checklist
> Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.

- **Pattern selection**: Survey orchestration typically runs **pipeline** (brief → question design → sampling → monitoring → handoff). If question design + sampling prep run in parallel, note a **diamond** block with merge gate in the plan header.
- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing audience, goals, sampling logic, dependency graph (legal, CS, research ops), error handling, and success metrics (response rate, completion %, demographic balance).
- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for MAP automation diffs, Context7 for research SOPs + historic surveys, Sequential Thinking for pre/post-readouts, Playwright for survey QA.
- **Guardrails**: Default retry limit = 2 for distribution/QA failures; escalation ladder = Research Lead → Customer Marketing → Exec sponsor.
- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before launch to confirm dependencies, approvals, deliverables.

## Workflow
1. **Brief Assembly** – capture goals, personas, hypotheses, and stakeholder approvals.
2. **Question Design** – generate question bank with logic, scales, and branching recommendations.
3. **Sampling & Distribution** – build target lists, dedupe suppression lists, schedule sends.
4. **Monitoring** – track response rates, data quality, and audience balance; trigger boosts if needed.
5. **Handoff** – package clean dataset + metadata for `synthesize-feedback` command.

## Outputs
- Survey plan (audience, sample, channels, incentive, timeline).
- Question set with logic map and translation/localization notes.
- Distribution checklist + automation steps for MAP/CS tooling.
- Plan JSON entry stored/updated in `.claude/plans` for audit trail.

## Agent/Skill Invocations
- `research-lead` – validates methodology and question quality.
- `cs-analyst` – ensures sampling + data integrity.
- `survey-design` skill – provides templates and guardrails.
- `stakeholder-ops` skill – outlines approvals + comms.

## GTM Agents Safeguards
- **Fallback agents**: document substitutes (e.g., CS Analyst covering Research Lead) when leads unavailable.
- **Escalation triggers**: if response rate misses guardrail twice or sampling bias detected, escalate via GTM Agents rip-cord and log corrective actions in plan JSON.
- **Plan maintenance**: update plan JSON/change log when audiences, question sets, or tooling stacks change to preserve audit parity.

---

© gtmagents · Apache-2.0 · gtmagents/gtm-agents

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set224

The whole set →
measure-engagement measure-engagement pulls community health metrics, sentiment, and experiment results into one report with a prioritized action list. Use it when you need to see what is happening in a community and what to do about it. CX Codex +1 ★ 450repo stars prioritize-gaps prioritize-gaps scores customer journey friction points, assigns owners, and creates remediation roadmaps. Helps teams prioritize fixes across onboarding and lifecycle stages. CX Codex +1 ★ 450repo stars map-journey map-journey — a Claude Code command that runs a structured journey mapping workshop, from research compilation to a gap log with assigned owners. Takes persona, scope, and time horizon as inputs. CX Codex +1 ★ 450repo stars plan-community-calendar plan-community-calendar builds a community programming calendar spanning 8 weeks or a quarter, with themes, formats, owners and dependencies. CX Codex +1 ★ 450repo stars configure-rules The configure-rules command takes personalization rules through data checks, decision setup, variant mapping, QA, and deployment. Use it to prepare changes for web and in-app channels. CX Codex +1 ★ 450repo stars forecast-renewals forecast-renewals — a command that builds segmented renewal forecasts with account health signals, variance analysis, and executive reporting. Combines ARR, NRR, and risk data into a single view. CX Codex +1 ★ 450repo stars experiment-design-kit experiment-design-kit structures product and growth hypotheses into test briefs with guardrails, variant catalogs, and rollback plans. CX Codex +1 ★ 450repo stars run-community-event run-community-event is a Claude Code command that drafts an agenda, moderation plan, and follow-up tasks for a community session or livestream. CX Codex +1 ★ 450repo stars

Project sponsors

Companies that keep this analytics open