Feedback Theme Synthesizer
Turn tickets, churn reasons, call notes, and request boards into ranked problem themes counted by distinct accounts and revenue at stake.
Before & after
Same prompt, same agent — the only difference is the skill.
Customer success is really important for retention. You'll want to think about what your customers need most and how your product can support them. Some companies focus on onboarding, others on ongoing support and feature education. You could look at your churn data and try to identify patterns. It might help to talk to customers directly to understand their pain points. You'd want to create a plan that addresses those issues, maybe through product improvements or better support. There are lots of approaches you could take depending on your specific situation.
CS PRODUCT STRATEGY FRAMEWORK RETENTION ANALYSIS → Cohort 1 churn: 35% at month 3 (below 25% target) → Root cause: Customers not completing onboarding by day 7 → Secondary: No in-app health score for at-risk accounts STRATEGIC PILLARS 1. ONBOARDING REDESIGN → Current: 12-step wizard (45% completion) → Target: 3-step critical path (80% completion) → Timeline: 4 weeks → Expected impact: -8% Month 3 churn 2. IN-APP HEALTH SIGNALS → Real-time engagement scoring → Triggers CS outreach when score drops 20%+ → Timeline: 6 weeks → Expected impact: -6% Month 3 churn 3. FEATURE ADOPTION TRACKING → Dashboard showing usage vs subscription tier → Auto-flag underutilized features for CS coaching → Timeline: 3 weeks → Expected impact: -5% Month 3 churn PRIORITY ROADMAP Q3: Onboarding redesign (highest ROI) Q4: Health scoring system Q1 2026: Feature adoption coaching SUCCESS METRICS → Month 3 churn: 25% (from 35%) → Onboarding completion: 80% → Health score accuracy: 88% (predicts churn)
About this skill
Plain feedback summaries overweight the loudest customer and restate feature requests as if they were problems. This skill turns raw feedback into a short list of problem themes you can defend in a roadmap meeting.
What it does
- Counts distinct accounts, not mentions, and always shows the denominator
- Weights themes by segment, plan tier, and revenue actually at stake in the data
- Translates requested solutions into underlying problem statements
- Flags source bias: churn surveys, lost-deal notes, and voting boards
- Keeps high-stakes one-offs separate from real patterns
What you get
A ranked theme table (accounts, mentions, segments, revenue at stake, trend, confidence), verbatim evidence per theme, open questions with how to check them, and data caveats.
Best for
Product and customer-success leads preparing quarterly roadmap input or a voice-of-customer review from tickets, calls, and surveys.
SKILL.md preview
---
name: feedback-theme-synthesizer
description: Turn a pile of raw customer feedback - support tickets, sales call notes, churn reasons, NPS comments, feature request boards, interview notes - into deduplicated, evidence-weighted themes with account counts, revenue at stake, representative quotes, and a problem statement for each, so product decisions rest on patterns rather than the loudest voice. Use when the user says "what are customers actually asking for?", "summarize these tickets", "theme this feedback", "why are people churning?", "the export complaint keeps coming up, is it real?", "make sense of our feature request board", or "what should we tell leadership customers want?".
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Product Practice Diagnostic
Trace a product-team symptom (unused features, roadmap churn, priority fights) to the broken stage of the loop and fix one thing first.
Feature Launch Go-to-Market Plan
Plan one feature launch: tier, plan access, audience messages, readiness gates for support, sales, billing, and docs, and success metrics.
Pricing Tier and Packaging Diagnosis
Finds why your pricing tiers underperform and redesigns value metric, fences, price gaps, and upgrade triggers with a migration plan.
Product Specs, Roadmaps, and Research Decisions
Turn customer evidence into testable PRDs, dependency-aware roadmaps, and stakeholder updates with clear decisions and tradeoffs.