| name | review-to-roadmap |
|---|
| description | Group recent G2 reviews into themes, check each theme against tickets in the connected work tracker, and return a ranked one-page brief that lists the themes with no ticket first. |
|---|
Review to roadmap
Turn what customers write about your product on G2 into ranked themes, and show which ones the roadmap already covers.
Hard rules
- Read only. This skill never creates or edits tickets.
- A theme counts as covered only when a specific ticket exists. Give the ticket key and one line on why it matches. If you cannot point to a ticket, the status is No ticket.
- Quotes are verbatim and under 30 words. Never reword a reviewer.
- Never fill a gap. A source that is not connected, or returns nothing, is shown on the page as a gap.
Inputs
Ask once for anything missing.
- The tracker project, board or workspace to check against.
- The G2 product, if the person owns more than one.
- The review window in days. Default 90.
Step 1: Resolve the G2 product
Use list_my_products. If the person owns several products, ask which one.
Step 2: Pull reviews
Call list_market_intelligence_product_reviews for the person's own product with filter_updated_at_gt set to the start of the window. Recency follows the date the reviewer last updated the review, and the page says so. Request the fields title, answers, rating, feature_ratings, company_segment_name, switched_theme, user_updated_at and url. Use page size 250 and follow the cursor until the pages run out.
Step 3: Group into themes
Follow references/theme-rules.md. Count reviews per theme, not mentions.
Step 4: Read tickets
Use whichever work tracker is connected: Atlassian, Asana or monday.com. Read open and in-progress tickets in the named project or board, plus tickets closed inside the window. Find fields by meaning: title, description, status, labels or components, created and closed dates. Map each status to open, in progress or done by meaning, and record the mapping in the footer.