run-member-insight-sprint command for Claude Code
run-member-insight-sprint runs a short community research sprint over forums, interviews and surveys, then routes what it finds to the people who asked.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/run-member-insight-sprint.mdWhat run-member-insight-sprint does
A slash command for Claude that runs a member research sprint. It drafts the questions and a sampling plan per channel, collects answers from forums, AMAs, micro-surveys and one-to-one interviews, then tags the material by persona, motivation, sentiment and urgency before writing the readout.
Four flags set the frame. --theme picks the topic, --sample names the cohorts, --window gives the sprint length and --audience lists the stakeholders who get the results. A fifth flag, --evidence, is optional and takes threads, tickets or recordings you already have. Leave out --audience and the routing step has nowhere to send the findings.
Output is a deck or memo with top findings, a tagged dataset with member story snippets, and an action tracker with owners and deadlines. The agents member-insights-advocate and community-ecosystem-strategist lead the work, backed by the community-insight-taxonomy and closed-loop-community-playbook skills.
What it helps with
- plan questions and a sampling frame before the sprint starts
- pool answers from forum threads, interviews and micro-surveys into one dataset
- tag quotes by persona, motivation and urgency
- write a readout with findings and quotes for a named stakeholder
- track follow-up actions with owners and due dates
Example prompts for the agent
- Start the onboarding sprint:
/community-building:run-member-insight-sprint --theme onboarding --sample champions,builders --window 21d --audience product,marketing - Run a 14-day sprint on integrations for champions and partners, readout for product and cs:
/community-building:run-member-insight-sprint --theme integrations --sample champions,partners --window 14d --audience product,cs - Do an advocacy sprint over 21 days and send it to exec and the community team:
/community-building:run-member-insight-sprint --theme advocacy --sample execs,partners --window 21d --audience exec,community
How to install run-member-insight-sprint
Manually: put the files in place
.claude/commands/run-member-insight-sprint.mdCall it with /run-member-insight-sprint. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/run-member-insight-sprint.mdCall it with /prompts:run-member-insight-sprint. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/run-member-insight-sprint.prompt.mdManually: put the files in place
.gemini/commands/run-member-insight-sprint.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about run-member-insight-sprint
How to install run-member-insight-sprint in Claude Code?
Copy run-member-insight-sprint.md into .claude/commands/ in your project. You then call it as /community-building:run-member-insight-sprint with the flags you need.
What does run-member-insight-sprint do?
It runs a member research sprint: sets the questions and sampling, gathers signals from several channels, tags them and produces a readout with recommended actions. You also get a tagged dataset and an action tracker.
Which flag is optional?
--evidence. It takes threads, tickets or recordings you already have. The other four flags define the sprint itself.
Source text
run-member-insight-sprint.md · Apache-2.0
--- name: run-member-insight-sprint description: Executes a rapid member insight sprint across forums, interviews, and surveys with routing plan. usage: /community-building:run-member-insight-sprint --theme onboarding --sample champions,builders --window 21d --audience product,marketing --- # Command: run-member-insight-sprint ## Inputs - **theme** – focus topic (onboarding, ai-use-cases, integrations, advocacy, support). - **sample** – member cohorts to include (champions, builders, execs, partners, lurkers). - **window** – sprint duration (7d, 14d, 21d, custom). - **audience** – comma-separated stakeholders for readout (product, marketing, cs, exec, community). - **evidence** – optional list of threads, tickets, or recordings to ingest. ## Workflow 1. **Sprint Setup** – define questions, sampling plan, and instrumentation across channels. 2. **Signal Collection** – launch prompts, AMAs, micro-surveys, and 1:1 interviews. 3. **Tagging & Analysis** – apply taxonomy for personas, drivers, sentiment, urgency. 4. **Narrative & Actions** – craft insight summary, quotes, data, and recommended actions per audience. 5. **Follow-up & Routing** – create action register, assign owners, and message members on outcomes. ## Outputs - Insight sprint report (deck/memo) with top findings, quotes, and metrics. - Tagged dataset + member story snippets for reuse. - Action tracker linking insights to owners, deadlines, and follow-up comms. ## Agent/Skill Invocations - `member-insights-advocate` – leads data capture, tagging, and storytelling. - `community-ecosystem-strategist` – aligns insights to strategic priorities. - `community-insight-taxonomy` skill – enforces tagging standards. - `closed-loop-community-playbook` skill – manages routing + member follow-up. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents