Customer Feedback to Roadmap Generator

Goal

Deliver a complete transformation of customer feedback into:

1. a Theme analysis table,
2. a priority-ranked list of initiatives,
3. a sprint-based visual roadmap, and
4. a concise stakeholder update that explains objectives, timeline, and asks.

Inputs to gather

• feedback data (the raw NPS comments, support tickets, surveys—needed for analysis)
• sprint length in weeks (determines roadmap cadence)
• max initiatives to include (caps roadmap size)

Before doing any work, ask the user for these inputs in ONE message. Skip anything they already provided. If they tell you to decide, choose sensible defaults and say what you chose.

Workflow

1. Parse feedback data: deduplicate entries. For each unique comment, tag Product Area, Theme, and Emotional Tone (positive, neutral, negative). Calculate, per Theme, Frequency and Avg Sentiment (–1 to +1). Output a markdown table: Theme | Product Area | Frequency | Avg Sentiment.
   • Check with the user that tagging looks reasonable before proceeding.

2. From that table, select the 8–12 Themes with highest Frequency that have negative Avg Sentiment (or all if fewer than 8). For each, propose one Initiative (one-sentence description) and list assumed Success Metric(s). Output a markdown table: ID | Initiative | Target Theme | Success Metric.

3. For each initiative, assign:
   • Impact score (1–5) based on potential NPS lift or ticket reduction.
   • Effort score (1–5) where 1 = very low engineering effort, 5 = very high.
   • Priority = Impact – Effort.
   Output a markdown table sorted by Priority descending.

4. Select up to max initiatives with the highest Priority. Allocate them into sequential sprints of the given sprint length, allowing a maximum of two major initiatives per sprint and bundling any minor items (<3 story points). For each sprint, define Sprint Goal, Included Initiative IDs, Key Deliverables, and Risks/Mitigations.
   • Produce (A) a Sprint Plan markdown table.
   • Produce (B) a simple textual Gantt chart: rows = sprints, columns = weeks, cells list Initiative IDs.

5. Craft an executive-level stakeholder update (≤250 words) summarizing:
   • Overall objective.
   • Top three high-impact initiatives and expected customer outcomes.
   • Total timeline (number of sprints × sprint length weeks).
   • Next steps and any stakeholder asks.

Output

A single document containing, in order:

1. Theme Analysis Table
2. Initiative Proposal Table
3. Scored Initiatives Table (sorted by Priority)
4. Sprint Plan Table
5. Textual Gantt view
6. ≤250-word stakeholder update summary

All tables in markdown format; stakeholder update as plain text paragraph(s).