Customer feedback to themes and roadmap asks: Multi-Step Agent Workflow for Claude Code, Codex or ChatGPT

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.

Prompt

Installs to .agents/skills/customer-feedback-to-themes-and-roadmap-asks-multi-step-agent-wo/

mkdir -p .agents/skills/customer-feedback-to-themes-and-roadmap-asks-multi-step-agent-wo && curl -sL "https://prompts-gpt.com/prompts/customer-feedback-to-themes-and-roadmap-asks-multi-step-agent-workflow-for-claude-code-codex-or-chat/raw" -o .agents/skills/customer-feedback-to-themes-and-roadmap-asks-multi-step-agent-wo/SKILL.md
SKILL.md
Preview
---
name: customer-feedback-to-themes-and-roadmap-asks-multi-step-agent-wo
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."
---

# Customer feedback to themes and roadmap asks: Multi-Step Agent Workflow for Claude Code, Codex or ChatGPT

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.

## Prompt

```
---
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.
```

## Usage Notes

Run it in Claude Code or Codex: save as .claude/skills/customer-feedback-theme-report/SKILL.md (or .agents/skills/ for Codex) and say "run the Customer feedback to themes and roadmap asks workflow"; parallel steps run as subagents. Or paste it into ChatGPT or Claude and answer its questions. It asks for: feedback, product_context, roadmap, competitors. Build or run it step by step at prompts-gpt.com/workflows/customer-feedback-theme-report.

Example output

At a glanceLedgerly problem themes by row count84 NPS comments, ranked by opportunity score
  • Slow CSV export: 19 rows (23%)
  • Reminder timing control: 14 rows (17%)
  • Mobile invoice editing: 11 rows (13%)
  • Multi-currency totals: 8 rows (10%)
  • Onboarding bank link: 7 rows (8%)

Example for: 84 NPS comments for Ledgerly (invoicing for freelancers), roadmap "Q1: faster export, Stripe payouts; Q2: mobile redesign", competitors FreshBooks and Wave.

Ledgerly Feedback Report: Q4 NPS Comments

Status: Draft. Waiting for approval (Step 9). Please spot-check the quotes in verified before sharing.

1. Summary

  • 84 rows were kept and 3 dropped (2 duplicates, 1 empty). All 84 rows carry at least one theme.
  • Slow/failed CSV export is the top problem: 19 rows (23%), average severity 3.2.
  • Payment reminder timing affects 14 rows (17%), mostly Pro plan users.
  • Mobile invoice editing appears in 11 rows (13%). 8 of them are severity 3 or higher.
  • Fast invoice creation is the top praise theme, with 22 rows (26%).

2. Problem Themes (by opportunity score)

ThemeRowsShareAvg severityScoreSegmentsTrend
Slow CSV export1923%3.260.8Pro, Team↑ Oct→Dec
Reminder timing control1417%2.940.6Proflat
Mobile invoice editing1113%3.134.1Free, Pro↑
Multi-currency totals810%3.528.0Teamflat
Onboarding bank link78%2.618.2Free↓

3. Top Insights

  1. Exports of large months fail. 19 rows (R4, R17, R52). Quote: "Export to CSV takes minutes and times out on big months" (R4).
  2. Reminders can't be scheduled the way users want. 14 rows (R9, R33). Quote: "reminders go out on weekends and annoy my clients" (R33).
  3. Editing an invoice on a phone fails. 11 rows (R21, R60). Quote: "can't change line items on my phone, have to wait till I'm home" (R60).
  4. Invoices in mixed currencies produce wrong totals. 8 rows (R12, R71). Quote: "dashboard adds EUR and USD like they're the same" (R71).
  5. Linking a bank account stalls new users. 7 rows (R2, R40). Quote: "got stuck linking my bank on day one" (R2).

4. Roadmap Asks

ProblemEvidenceSuccess measureStatus
Users can't export a full busy month19 rows, R4Export completes for 12-month rangeOn roadmap (Q1)
Users can't control when reminders send14 rows, R33Reminder complaints halveNew
Users can't edit invoices on mobile11 rows, R60Mobile edit success ratePartly (Q2 redesign)
Users can't trust multi-currency totals8 rows, R71Zero currency-mix ticketsNew
New users can't finish bank linking7 rows, R2Day-1 link completionNew

5. What's Working

  • Fast invoice creation: 22 rows. Quote: "invoice out in 30 seconds" (R15).
  • Clean invoice design: 12 rows.
  • Responsive support: 9 rows.

6. Market Context

I read 41 reviews. G2 was blocked, so it isn't included. In FreshBooks reviews, users praise the mobile app ("best invoicing app on iOS", trustpilot.com/review/freshbooks.com). In Wave reviews, a common complaint is slow export, which overlaps with our top theme ("exports hang forever", reddit.com/r/smallbusiness/…).

7. Caveats

  • The sample is small: 84 rows from a single NPS survey.
  • Detractors are likely over-represented, since they tend to write longer comments.
  • The Team segment has only 9 rows, which is too few to draw conclusions.
  • 13 rows have an unknown segment.
  • These counts don't support any claims about churn or revenue.
Written by AI from this prompt. Your results will vary.

Run it in Claude Code or Codex: save as .claude/skills/customer-feedback-theme-report/SKILL.md (or .agents/skills/ for Codex) and say "run the Customer feedback to themes and roadmap asks workflow"; parallel steps run as subagents. Or paste it into ChatGPT or Claude and answer its questions. It asks for: feedback, product_context, roadmap, competitors. Build or run it step by step at prompts-gpt.com/workflows/customer-feedback-theme-report.

Make it repeatable

Keep using this prompt without pasting it in every time.

Prompt details

By
Prompts-GPT editors
Published
How prompts are written and checked

Did this prompt work?

Keep exploring

More in Multi-Agent Pipelines