Skill · Workflow

customer-feedback-theme-report

Tags pasted reviews, NPS comments or tickets in parallel chunks, clusters them into counted themes, backs each theme with verbatim quotes, optionally compares competitors' public reviews, and writes a ranked report with roadmap asks framed as problems. Use when asked to run the "Customer feedback to themes and roadmap asks" workflow.

The skill itself. Agents read the name and description first and load the rest only when a task matches.

customer-feedback-theme-report/SKILL.md
---
name: customer-feedback-theme-report
description: Tags pasted reviews, NPS comments or tickets in parallel chunks, clusters them into counted themes, backs each theme with verbatim quotes, optionally compares competitors' public reviews, and writes a ranked report with roadmap asks framed as problems. Use when asked to run the "Customer feedback to themes and roadmap asks" workflow.
---

# Customer feedback to themes and roadmap asks

Tags pasted reviews, NPS comments or tickets in parallel chunks, clusters them into counted themes, backs each theme with verbatim quotes, optionally compares competitors' public reviews, and writes a ranked report with roadmap asks framed as problems.

## Inputs

Ask for any of these that the user hasn't given:

- `feedback` (e.g. "Paste one piece of feedback per line, with any metadata, e.g. 'NPS 3 | plan: Pro | 2026-10-04 | Export to CSV takes minutes and times out on big months'")
- `product_context` (e.g. "Ledgerly, invoicing for freelancers. Areas: invoices, reminders, payments, export, mobile app, onboarding.")
- `roadmap` (e.g. "Q1: faster export, Stripe payouts. Q2: mobile app redesign. (or 'none')")
- `competitors` (e.g. "FreshBooks, Wave (or 'none' to skip public reviews)")

## Steps

Run the steps in order. Refer to saved results by name. Don't skip a step that says STOP.

1. **Paste the feedback** — Start: Paste {{feedback}} (reviews, NPS comments, survey answers or a ticket export) with {{product_context}}, your {{roadmap}} and optional {{competitors}}. Remove customer emails and names first if the report will be shared.
2. **Number and clean the rows** — Turn {{feedback}} into a numbered list R1, R2…, one row per piece of feedback. Keep the exact text: do not shorten, translate or fix spelling. Keep any metadata on the row (score, plan, date, channel, segment) as key: value. Drop empty rows and exact duplicates. End with: rows kept, rows dropped (and why), which metadata fields exist, and the rows split into four even ranges labelled Chunk 1 to Chunk 4 (e.g. Chunk 1 = R1–R50). If there are fewer than 20 rows, put them all in Chunk 1 and mark Chunks 2–4 empty. Save the result as `rows`.
3. **Tag rows in parallel** — Launch these as parallel subagents in one message, then wait for all of them. Tag the rows in {{rows}} that fall in your chunk (the ranges are listed at its end). For each row write one line: ID | sentiment (positive, mixed, negative) | theme (a 2–4 word noun phrase naming the underlying need, e.g. 'slow CSV export', not 'bad') | feature (an area from {{product_context}}, or 'general') | segment (only from the row's metadata, else 'unknown') | severity (1 = cosmetic, 2 = annoyance, 3 = blocks a task, 4 = threatens churn or money; 'n/a' for praise). A row may have up to 2 themes. Tag only what the row says. If your chunk is empty, write 'No rows in this chunk.' Save the result as `tags`.
   - **Chunk 1**: Tag every row in Chunk 1.
   - **Chunk 2**: Tag every row in Chunk 2.
   - **Chunk 3**: Tag every row in Chunk 3.
   - **Chunk 4**: Tag every row in Chunk 4.
4. **Public reviews (optional)** — If {{competitors}} is empty or says 'none', reply 'Skipped: no competitors given.' and stop. Otherwise, for each competitor, search for reviews from the last 12 months on G2, Capterra, Trustpilot, the App Store, Google Play and Reddit. Some review sites block automated reading: list which ones you couldn't open and use only pages you could read. Report the 3 most common complaints and 2 most common praises you saw, each with 1–2 short verbatim quotes and the URL. Then say which of them overlap with themes in {{tags}}. Do not estimate counts you didn't see; say how many reviews you actually read. Save the result as `public`.
5. **Cluster into themes** — Merge the theme labels in {{tags}} into 6–12 themes. Combine labels that describe the same need; keep a theme separate if fixing it would take different work. For each theme give: name, one-sentence definition, row count (a row counts once per theme), share of all rows, sentiment split, average severity (ignoring 'n/a'; write 'praise' if all rows are n/a), top segments, main feature, and the full list of row IDs. Put themes with fewer than 2 rows into 'Long tail' with their IDs. Finally, state how many rows have at least one theme and confirm it matches the count in {{rows}}; if it doesn't, say which IDs are missing. Save the result as `themes`.
6. **Verify with quotes** — For each theme in {{themes}}: pick 2–3 rows from its ID list and copy their text from {{rows}} word for word, with the ID. Prefer rows from different segments. Then re-read 5 IDs from the theme's list and check they fit the definition; if more than 1 of the 5 doesn't fit, re-check the whole list and correct the count. Drop any theme without 2 supporting rows and say why. Return the verified theme table (same columns as before, corrected counts) and the quotes under each theme, then a 'Changes' list. Save the result as `verified`.
7. **Write insights and roadmap asks** — From {{verified}}, and {{public}} if it has data, write the report for {{product_context}}:
1. Summary: 5 bullets, each a finding with a number.
2. Problem theme table sorted by opportunity score = row count × average severity (praise themes go in section 5, not here): Theme | Rows | Share | Avg severity | Score | Segments | Trend (only if dates exist).
3. Top 5 insights: what users struggle with, who, how badly, and evidence (count, row IDs, one quote).
4. Roadmap asks for the top 5 problem themes: a problem statement (not a solution), the evidence, a success measure, and status against {{roadmap}} (on roadmap, partly, or new).
5. What's working: the top 3 praise themes.
6. Market context from public reviews, if any, with URLs.
7. Caveats: sample size, source bias (e.g. reviews skew negative), segments with too few rows to conclude, and how many rows were 'unknown' segment.
Use only numbers from {{verified}}. Save the result as `report`.
8. **Check the report** — Review loop (max 3 passes): 1. Every insight and roadmap ask states a row count and at least one row ID (R-number).
2. Every quote is in quotation marks and followed by a row ID.
3. Every opportunity score equals rows × average severity (recompute each one).
4. Roadmap asks are written as problems ('users can't export a full year') not solutions ('build async export').
5. A Caveats section exists and states the sample size.
6. No claims about causes, revenue or churn rates that the counts can't show.
7. Under 1,200 words, not counting tables. Save the result as `report`.
9. **Approve the report** — STOP and ask the user to approve before continuing: Review {{report}} and spot-check a few quotes in {{verified}} against your source data. Approve, edit or reject before sharing.
10. **Save the report and theme table** — Finish: Return {{report}} and {{verified}}.

## Done when

Every step has run, each approval was given, and you've reported what was produced and where it was saved.