{"id":"res-pm-ticket-feature-request-tally","audience":"product-managers","category":"research","technique":"grounding","title":"Tally feature requests from support tickets, with ticket IDs","free":false,"task":"Before roadmap planning, you want to know which features customers actually asked for in last week's support tickets. You want exactly 3 numbered lines for the top 3 requests, each with its count and the ticket IDs, like \"Bulk export: 3 (T-102, T-108, T-111)\". Count only explicit requests, not bug reports or praise, use only the tickets, plain text, nothing else.","materialLabel":"Last week's support tickets (attached to your prompt automatically)","material":"SUPPORT TICKETS - Week of Oct 26 (Stackwise project management app)\n\nT-201: \"Can you add a dark mode? My eyes hurt at night.\"\nT-202: \"The export button crashes on Safari.\" (bug)\nT-203: \"Please let us assign one task to two people.\"\nT-204: \"Love the new board view, great work!\"\nT-205: \"Any plans for dark mode?\"\nT-206: \"We need tasks with multiple assignees for pair work.\"\nT-207: \"Would be great to export reports to PDF.\"\nT-208: \"Dark mode please!!\"\nT-209: \"Time tracking inside tasks would save us a separate tool.\"\nT-210: \"Multiple assignees per task, please.\"\nT-211: \"Notifications are late by 10 minutes.\" (bug)\nT-212: \"Exporting to PDF would help our client reports.\"\n\nSales note: \"a big prospect asked about time tracking on a call\" (not a ticket)","rules":[{"type":"numberedItems","count":3},{"type":"plainText"}],"mistakes":[{"title":"Mixing bugs with requests","why":"The export crash and late notifications look like feature asks to the AI.","fix":"Say: \"Count only explicit feature requests, not bugs or praise.\"","checks":["r1"]},{"title":"Counting the sales note","why":"The prospect's ask is in your notes, so the AI may bump time tracking up.","fix":"Add: \"Use only the tickets.\"","checks":["r2","r1"]},{"title":"No ticket IDs","why":"Without IDs, you can't pull the tickets into the roadmap doc.","fix":"Show it: \"Format: Feature: N (T-201, T-205).\"","checks":["r1","r0"]},{"title":"Not saying how many","why":"The AI decides the length itself and usually returns more lines than you can use.","fix":"Be exact: \"exactly 3 numbered lines.\"","checks":["numberedItems"]},{"title":"Getting markdown back","why":"AI defaults to bold labels and headings, which show up as stray symbols in the roadmap doc.","fix":"Ask for \"plain text, no bold, no headings.\"","checks":["plainText"]}],"promptHints":[{"label":"Asks for counts and IDs","patterns":["count","ticket ids?","T-\\d","how many"]},{"label":"Excludes bugs and praise","patterns":["bug","praise","explicit request","not (bugs|praise)"]},{"label":"Says to use only your sources","patterns":["only.{0,40}(tickets)","no outside","(don't|do not) (add|invent|guess|use (your|outside))","nothing (that's |that is )?not in"]},{"label":"Says exactly how many","patterns":["\\b(3|three)\\b.{0,25}(line|request|feature)","exactly \\d+"]},{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]}],"hint":"A request count is only useful if it's clean. Tell the AI what counts as a request, where to look, and to show the ticket IDs behind each number.","rubricLabels":["The 3 requests are dark mode (3: T-201, T-205, T-208), multiple assignees (3: T-203, T-206, T-210) and PDF export (2: T-207, T-212), with correct counts","Each line lists the correct ticket IDs, and no bug ticket (T-202, T-211), praise ticket (T-204) or the sales note is counted","Outputs only the 3 numbered lines: no intro, no prioritization advice, no mention of time tracking as a top request"]}