From bd4e235b9b7f0f61975bd736b219ed6d036d8389 Mon Sep 17 00:00:00 2001
From: Zhongwei Li <lizhongwei.nkcs@gmail.com>
Date: Sat, 29 Nov 2025 18:30:14 +0800
Subject: [PATCH] Initial commit

---
 .claude-plugin/plugin.json        | 24 ++++++++++
 README.md                         |  3 ++
 agents/cs-analyst.md              | 27 +++++++++++
 agents/product-liaison.md         | 27 +++++++++++
 agents/research-lead.md           | 29 ++++++++++++
 commands/route-insights.md        | 49 ++++++++++++++++++++
 commands/run-survey.md            | 50 ++++++++++++++++++++
 commands/synthesize-feedback.md   | 49 ++++++++++++++++++++
 plugin.lock.json                  | 77 +++++++++++++++++++++++++++++++
 skills/insight-synthesis/SKILL.md | 31 +++++++++++++
 skills/stakeholder-ops/SKILL.md   | 31 +++++++++++++
 skills/survey-design/SKILL.md     | 31 +++++++++++++
 12 files changed, 428 insertions(+)
 create mode 100644 .claude-plugin/plugin.json
 create mode 100644 README.md
 create mode 100644 agents/cs-analyst.md
 create mode 100644 agents/product-liaison.md
 create mode 100644 agents/research-lead.md
 create mode 100644 commands/route-insights.md
 create mode 100644 commands/run-survey.md
 create mode 100644 commands/synthesize-feedback.md
 create mode 100644 plugin.lock.json
 create mode 100644 skills/insight-synthesis/SKILL.md
 create mode 100644 skills/stakeholder-ops/SKILL.md
 create mode 100644 skills/survey-design/SKILL.md

diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json
new file mode 100644
index 0000000..3270f54
--- /dev/null
+++ b/.claude-plugin/plugin.json
@@ -0,0 +1,24 @@
+{
+  "name": "customer-feedback-orchestration",
+  "description": "Customer feedback orchestration covering research, synthesis, and stakeholder workflows",
+  "version": "1.0.0",
+  "author": {
+    "name": "GTM Agents",
+    "email": "opensource@intentgpt.ai"
+  },
+  "skills": [
+    "./skills/survey-design/SKILL.md",
+    "./skills/insight-synthesis/SKILL.md",
+    "./skills/stakeholder-ops/SKILL.md"
+  ],
+  "agents": [
+    "./agents/research-lead.md",
+    "./agents/product-liaison.md",
+    "./agents/cs-analyst.md"
+  ],
+  "commands": [
+    "./commands/run-survey.md",
+    "./commands/synthesize-feedback.md",
+    "./commands/route-insights.md"
+  ]
+}
\ No newline at end of file
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..f6ec9bb
--- /dev/null
+++ b/README.md
@@ -0,0 +1,3 @@
+# customer-feedback-orchestration
+
+Customer feedback orchestration covering research, synthesis, and stakeholder workflows
diff --git a/agents/cs-analyst.md b/agents/cs-analyst.md
new file mode 100644
index 0000000..039f43b
--- /dev/null
+++ b/agents/cs-analyst.md
@@ -0,0 +1,27 @@
+---
+name: cs-analyst
+description: Aggregates quantitative feedback data, detects trends, and quantifies impact for GTM and product teams.
+model: haiku
+---
+
+# CS Analyst Agent
+
+## Responsibilities
+- Centralize survey responses, NPS, support tickets, product usage, and community sentiment.
+- Build dashboards tracking satisfaction, adoption blockers, and persona-level trends.
+- Quantify business impact of issues or requests (ARR at risk, expansion potential, efficiency gains).
+- Maintain feedback taxonomy and tagging hygiene across tools.
+
+## Workflow
+1. **Data Pipeline Maintenance** – ensure connectors, schema mappings, and refresh cadences remain healthy.
+2. **Signal Scoring** – categorize and score feedback by severity, frequency, persona, and ARR exposure.
+3. **Insight Packaging** – collaborate with `insight-synthesis` skill to craft narrative summaries.
+4. **Alerting** – trigger notifications for emerging risks or opportunities (feature demand spikes, sentiment drops).
+5. **Reporting** – publish weekly/monthly reports and support roadmap prioritization workshops.
+
+## Outputs
+- Feedback health dashboard with KPIs and heatmaps.
+- Alert digest summarizing top trends, risky cohorts, and recommended actions.
+- Clean datasets ready for product, CS, and marketing analytics work.
+
+---
diff --git a/agents/product-liaison.md b/agents/product-liaison.md
new file mode 100644
index 0000000..65b64b1
--- /dev/null
+++ b/agents/product-liaison.md
@@ -0,0 +1,27 @@
+---
+name: product-liaison
+description: Translates customer feedback into roadmap briefs, prioritization debates, and release communications.
+model: haiku
+---
+
+# Product Liaison Agent
+
+## Responsibilities
+- Partner with PMs to map feedback clusters into opportunity themes.
+- Maintain traceability between feedback artifacts and backlog items.
+- Facilitate prioritization discussions with data-backed narratives.
+- Ensure customer communications close the loop on shipped fixes or roadmap commitments.
+
+## Workflow
+1. **Signal Intake** – monitor synthesized insights, support trends, and community threads.
+2. **Theme Mapping** – align signals to roadmap epics, KPIs, and personas.
+3. **Prioritization Support** – prepare scoring, impact estimates, and customer voice snippets.
+4. **Execution Enablement** – coordinate design/eng/product on validation sessions and beta recruitment.
+5. **Communication Plan** – craft release notes, customer updates, and advocacy opportunities.
+
+## Outputs
+- Opportunity briefs linking insights to proposed solutions.
+- Prioritization scorecards with supporting evidence.
+- Customer update plan with messaging and owners.
+
+---
diff --git a/agents/research-lead.md b/agents/research-lead.md
new file mode 100644
index 0000000..9d8e4c0
--- /dev/null
+++ b/agents/research-lead.md
@@ -0,0 +1,29 @@
+---
+name: research-lead
+description: Designs multi-channel feedback programs and ensures signal quality across
+  surveys, interviews, and telemetry.
+model: haiku
+---
+
+
+# Research Lead Agent
+
+## Responsibilities
+- Define the research roadmap spanning surveys, interviews, product analytics, and community listening.
+- Maintain sampling plans, question banks, and methodology guardrails.
+- Partner with product, CS, and marketing stakeholders to align feedback goals with roadmap decisions.
+- Synthesize findings into actionable narratives and prioritize next steps.
+
+## Workflow
+1. **Intake & Alignment** – gather hypotheses, stakeholder questions, and target personas.
+2. **Program Design** – select methodologies, sample sizes, incentive plans, and tooling.
+3. **Execution Oversight** – monitor fielding progress, data quality, and response ratios.
+4. **Analysis & Storytelling** – guide `insight-synthesis` workflows and ensure outputs map to business objectives.
+5. **Follow-through** – create action trackers, influence roadmaps, and plan iteration cycles.
+
+## Outputs
+- Research brief with objectives, methodology, and timeline.
+- Survey/interview guides plus QA checklist.
+- Executive-ready readouts linking insights to roadmap decisions.
+
+---
diff --git a/commands/route-insights.md b/commands/route-insights.md
new file mode 100644
index 0000000..38a6394
--- /dev/null
+++ b/commands/route-insights.md
@@ -0,0 +1,49 @@
+---
+name: route-insights
+description: Operationalizes feedback themes by assigning owners, communication plans, and tracking loops.
+usage: /customer-feedback-orchestration:route-insights --themes file://themes.json --cadence monthly --channels "product,cs,marketing"
+---
+
+# Command: route-insights
+
+## Inputs
+- **themes** – JSON/CSV file or inline JSON containing prioritized themes from `synthesize-feedback`.
+- **cadence** – meeting or reporting cadence (weekly, biweekly, monthly).
+- **channels** – comma-separated functional audiences (product, cs, marketing, exec, community).
+- **broadcast** – true/false toggle to auto-generate comms templates for customers.
+- **tracking** – project tool identifier (asana, jira, notion) for action logging.
+
+### GTM Agents Pattern & Plan Checklist
+> Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.
+
+- **Pattern selection**: Insight routing generally runs **pipeline** (theme intake → owner mapping → action serialization → communications → feedback loop). If action serialization + comms can run in parallel, document a **diamond** block with merge gate in the plan header.
+- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing theme set, DRIs, dependency graph (product, CS, marketing, exec), error handling, and success metrics (resolution rate, time-to-close, comms completion).
+- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for workflow automation diffs, Context7 for past retros + roadmap docs, Sequential Thinking for follow-up cadence, Playwright for portal/comms QA if needed.
+- **Guardrails**: Default retry limit = 2 for task routing/comms failures; escalation ladder = Product Liaison → CX Leadership → Exec sponsor.
+- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before publishing to confirm dependencies, approvals, deliverables.
+
+## Workflow
+1. **Theme Intake** – validate scoring, persona coverage, and urgency tags.
+2. **Owner Mapping** – assign DRIs per functional area, define success metrics, and set deadlines.
+3. **Action Serialization** – create tasks/epics with references to supporting data and customer quotes.
+4. **Communication Plan** – craft internal/external messaging, executive summaries, and customer follow-ups.
+5. **Feedback Loop Setup** – configure progress dashboards, reminders, and close-the-loop alerts.
+
+## Outputs
+- Routing table (theme, owner, due date, metric, status).
+- Internal + external comms templates referencing impact and next steps.
+- Action tracker ready for import into chosen project tool.
+- Plan JSON entry stored/updated in `.claude/plans` for audit trail.
+
+## Agent/Skill Invocations
+- `product-liaison` – ensures roadmap alignment and executive visibility.
+- `cs-analyst` – verifies metrics + datasets tied to each action.
+- `stakeholder-ops` skill – governs approvals, cadences, and comms.
+- `insight-synthesis` skill – keeps narratives consistent with source data.
+
+## GTM Agents Safeguards
+- **Fallback agents**: document substitutes (e.g., CX Ops covering Product Liaison) when stakeholders unavailable.
+- **Escalation triggers**: if SLAs for close-the-loop breaching twice or roadmap owners reject actions repeatedly, escalate via GTM Agents rip-cord and log remediation inside plan JSON.
+- **Plan maintenance**: update plan JSON/change log when owners, cadences, or tracking tools change to maintain audit parity.
+
+---
diff --git a/commands/run-survey.md b/commands/run-survey.md
new file mode 100644
index 0000000..0d93951
--- /dev/null
+++ b/commands/run-survey.md
@@ -0,0 +1,50 @@
+---
+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.
+
+---
diff --git a/commands/synthesize-feedback.md b/commands/synthesize-feedback.md
new file mode 100644
index 0000000..8ad99d1
--- /dev/null
+++ b/commands/synthesize-feedback.md
@@ -0,0 +1,49 @@
+---
+name: synthesize-feedback
+description: Consolidates quantitative and qualitative signals into prioritized themes with opportunity sizing.
+usage: /customer-feedback-orchestration:synthesize-feedback --window 60d --personas "admins,execs" --detail workshop
+---
+
+# Command: synthesize-feedback
+
+## Inputs
+- **window** – analysis horizon (30d, 60d, quarter) pulling data from surveys, support, usage, community.
+- **personas** – optional filter for personas or segments to highlight.
+- **detail** – summary | workshop controls depth of deliverables.
+- **include-voice** – true/false to embed verbatim quotes.
+- **impact-lens** – arr | adoption | satisfaction to drive prioritization lens.
+
+### GTM Agents Pattern & Plan Checklist
+> Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.
+
+- **Pattern selection**: Feedback synthesis typically runs **pipeline** (aggregation → tagging → impact modeling → opportunity framing → narrative). If tagging + modeling can run in parallel, record a **diamond** block with merge gate in the plan header.
+- **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` capturing window, data feeds, dependency graph (CS, product, research, analytics), error handling, and success metrics (theme confidence, coverage %, time-to-synthesize).
+- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for taxonomy updates, Context7 for historic studies, Sequential Thinking for workshop prep, Playwright for dashboard QA when embedding outputs.
+- **Guardrails**: Default retry limit = 2 for data pulls/tagging jobs; escalation ladder = Research Lead → CX Leadership → Exec sponsor.
+- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before workshops to confirm dependencies + deliverables.
+
+## Workflow
+1. **Data Aggregation** – collect structured/unstructured feedback from connected systems.
+2. **Tagging & Clustering** – apply taxonomy, detect emerging topics, score severity + frequency.
+3. **Impact Modeling** – quantify ARR, usage, or sentiment impact with supporting metrics.
+4. **Opportunity Framing** – craft problem statements, desired outcomes, and proposed motions.
+5. **Narrative Packaging** – produce decks/notes for PM, CS, marketing, and exec consumption.
+
+## Outputs
+- Theme matrix with impact, personas, confidence, and owner recommendations.
+- Quote bank + evidence appendix tied to each theme.
+- Action backlog seeds for `route-insights` command.
+- Plan JSON entry stored/updated in `.claude/plans` for audit trail.
+
+## Agent/Skill Invocations
+- `cs-analyst` – leads data prep + scoring.
+- `research-lead` – ensures insights align with study goals.
+- `insight-synthesis` skill – provides framing templates and storytelling patterns.
+- `survey-design` skill – highlights methodology caveats.
+
+## GTM Agents Safeguards
+- **Fallback agents**: document substitutes (e.g., CS Analyst covering Research Lead) when leads unavailable.
+- **Escalation triggers**: if data completeness or confidence metrics miss thresholds twice, escalate via GTM Agents rip-cord and log remediation in plan JSON.
+- **Plan maintenance**: update plan JSON/change log when data sources, personas, or impact lenses change to preserve audit history.
+
+---
diff --git a/plugin.lock.json b/plugin.lock.json
new file mode 100644
index 0000000..d5c2e9b
--- /dev/null
+++ b/plugin.lock.json
@@ -0,0 +1,77 @@
+{
+  "$schema": "internal://schemas/plugin.lock.v1.json",
+  "pluginId": "gh:gtmagents/gtm-agents:plugins/customer-feedback-orchestration",
+  "normalized": {
+    "repo": null,
+    "ref": "refs/tags/v20251128.0",
+    "commit": "30586f1c22af1d20333cd43160e49bf0e42496d2",
+    "treeHash": "4c3336577d85966c4eaacf8ad83b4bb053ef3449d050195589f2dc58680a5df7",
+    "generatedAt": "2025-11-28T10:17:21.287576Z",
+    "toolVersion": "publish_plugins.py@0.2.0"
+  },
+  "origin": {
+    "remote": "git@github.com:zhongweili/42plugin-data.git",
+    "branch": "master",
+    "commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
+    "repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
+  },
+  "manifest": {
+    "name": "customer-feedback-orchestration",
+    "description": "Customer feedback orchestration covering research, synthesis, and stakeholder workflows",
+    "version": "1.0.0"
+  },
+  "content": {
+    "files": [
+      {
+        "path": "README.md",
+        "sha256": "49ef655701ff39e580de4aebf0faa0bd9142616318a953a87da0c2bb3f03bdbb"
+      },
+      {
+        "path": "agents/product-liaison.md",
+        "sha256": "2b18522f9629d94973e49a5171a02450fb15ea730384c67a01a4c1dc33e0f48b"
+      },
+      {
+        "path": "agents/research-lead.md",
+        "sha256": "e18c8cc2507a379c1458a70ef74ae867b3f0b2025babe8eb876a05961122e1bb"
+      },
+      {
+        "path": "agents/cs-analyst.md",
+        "sha256": "c192dacf30edd364a4091e969a29c9ce6450fa4b1560931dbd7cf14bcddfa435"
+      },
+      {
+        "path": ".claude-plugin/plugin.json",
+        "sha256": "1ba4cba3f6f75e7135ea7e18abb7d8aba7cea967db4119bcccfc35ab2c21b15f"
+      },
+      {
+        "path": "commands/run-survey.md",
+        "sha256": "b98afd1df4718c3110362989adbd328cc91c7f54f7c5bbf322bd9fe793b57f5c"
+      },
+      {
+        "path": "commands/route-insights.md",
+        "sha256": "7645c1f8eca13b036db0a4ff24ca7d3a16c49c50aabc562cd24247f6ab252292"
+      },
+      {
+        "path": "commands/synthesize-feedback.md",
+        "sha256": "c76f31eeb1c659652493ab2f5c1f63a75781bf5043337a0f433580406e4f2e5f"
+      },
+      {
+        "path": "skills/survey-design/SKILL.md",
+        "sha256": "7ca8606b4a9f99ea9e6a8ca9f051b6c6ad62e9498b44147ca4551c0202c34c28"
+      },
+      {
+        "path": "skills/stakeholder-ops/SKILL.md",
+        "sha256": "649133eaf3e06bcd1a7a1a28fd46abc4cfdc1a119703cbf2192e7bf749e88ce2"
+      },
+      {
+        "path": "skills/insight-synthesis/SKILL.md",
+        "sha256": "bddfa672757ffe03b2ca9f91b7eff266fbe90e2118949bf6d0597c5fbcb77a36"
+      }
+    ],
+    "dirSha256": "4c3336577d85966c4eaacf8ad83b4bb053ef3449d050195589f2dc58680a5df7"
+  },
+  "security": {
+    "scannedAt": null,
+    "scannerVersion": null,
+    "flags": []
+  }
+}
\ No newline at end of file
diff --git a/skills/insight-synthesis/SKILL.md b/skills/insight-synthesis/SKILL.md
new file mode 100644
index 0000000..899dbfb
--- /dev/null
+++ b/skills/insight-synthesis/SKILL.md
@@ -0,0 +1,31 @@
+---
+name: insight-synthesis
+description: Use to convert raw customer feedback into compelling narratives, themes,
+  and recommendations.
+---
+
+# Insight Synthesis Framework Skill
+
+## When to Use
+- Wrapping up research studies, surveys, or ongoing feedback programs.
+- Preparing executive readouts or roadmap recommendation docs.
+- Aligning cross-functional stakeholders on prioritized issues/opportunities.
+
+## Framework
+1. **Signal Stacking** – layer qualitative quotes, quantitative metrics, and behavioral data for each insight.
+2. **Theme Laddering** – cluster related findings into parent themes, mapping to personas and journeys.
+3. **Impact Assessment** – estimate business impact (ARR, adoption, satisfaction, efficiency) and confidence level.
+4. **Recommendation Crafting** – outline proposed actions, owners, and success metrics.
+5. **Storytelling** – build narrative arcs with hooks, evidence, and clear calls to action.
+
+## Templates
+- Insight card (context, signal evidence, impact, recommendation).
+- Executive summary outline with top themes and action table.
+- Appendix structure for quotes, charts, and methodology notes.
+
+## Tips
+- Keep verbatim quotes close to stats to reinforce credibility.
+- Use visual cues (heatmaps, journey overlays) to help audiences grasp patterns quickly.
+- Pair with `stakeholder-ops` to ensure follow-up actions are logged and tracked.
+
+---
diff --git a/skills/stakeholder-ops/SKILL.md b/skills/stakeholder-ops/SKILL.md
new file mode 100644
index 0000000..eee2732
--- /dev/null
+++ b/skills/stakeholder-ops/SKILL.md
@@ -0,0 +1,31 @@
+---
+name: stakeholder-ops
+description: Use to coordinate approvals, communications, and accountability across
+  teams for feedback programs.
+---
+
+# Stakeholder Operations Guide Skill
+
+## When to Use
+- Launching surveys, betas, or listening tours that require multi-team approvals.
+- Routing insights to product, CS, marketing, and exec stakeholders with clear accountability.
+- Ensuring follow-up communications and governance rituals stay on track.
+
+## Framework
+1. **Stakeholder Map** – list involved teams, decision rights, and expectations per stage.
+2. **Approval Workflow** – define checkpoints (brief sign-off, launch approval, readout review) with timelines.
+3. **Communication Plan** – specify audiences, channels, frequency, and owners for updates.
+4. **Action Tracking** – set up shared trackers with status, blockers, and success metrics.
+5. **Governance Rituals** – outline cadences (weekly syncs, monthly reviews) plus escalation paths.
+
+## Templates
+- RACI chart for research + activation workflows.
+- Approval checklist with required artifacts (brief, QA results, comms plan).
+- Meeting agenda + notes template to keep stakeholders aligned.
+
+## Tips
+- Keep stakeholder rosters fresh; note backups for vacations or org changes.
+- Automate reminders linked to due dates via project/workflow tools.
+- Pair with `insight-synthesis` outputs to ensure narrative consistency.
+
+---
diff --git a/skills/survey-design/SKILL.md b/skills/survey-design/SKILL.md
new file mode 100644
index 0000000..6be5f9b
--- /dev/null
+++ b/skills/survey-design/SKILL.md
@@ -0,0 +1,31 @@
+---
+name: survey-design
+description: Use to craft rigorous survey instruments with sampling, question logic,
+  and QA standards.
+---
+
+# 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
+1. **Objective Clarity** – define single-topic goals, hypotheses, and decision criteria.
+2. **Audience & Sampling** – specify personas, quotas, suppression rules, and incentive plan.
+3. **Question Architecture** – balance quant vs qual questions, avoid double-barreled prompts, include screener + validation items.
+4. **Logic & Branching** – outline conditional flows, progress indicators, and completion time targets.
+5. **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.
+
+---