{"id":"cs-feedback-vs-release-notes-status-table","audience":"managers","category":"support-work","technique":"verification","track":"support","level":"advanced","title":"Map customer requests to what actually shipped","free":false,"task":"Map the four customer requests to the release notes. Output a table with the header row exactly \"Request | Status | Shipped\" and four rows. Status is exactly Yes, No or Partly. Shipped is the release date or \"-\". Use only the release notes, not the sales claims. Plain text, table only, under 50 words.","materialLabel":"Your material (attached to your prompt automatically)","material":"CUSTOMER REQUESTS: R1 Bulk export. R2 Dark mode. R3 Failure alerts (email and Slack). R4 Custom roles.\n\nRELEASE NOTES (engineering, confirmed)\n- Oct 20: Bulk export of reports to CSV shipped to all plans.\n- Nov 2: Email alerts for report failures shipped. Slack alerts are in design; no date.\n- Nov 5: Custom roles in beta for Enterprise plans only. Other plans: not available.\n- Dark mode: under consideration; nothing shipped.\n\nSALES CLAIM: 'Dark mode shipped in October.' (False.)\nStatus rules: Yes = fully shipped to all customers who asked. Partly = some of it shipped, or shipped only to some plans. No = nothing shipped.","rules":[{"type":"plainText"},{"type":"maxWords","max":50}],"mistakes":[{"title":"Believing the sales claim","why":"Sales says dark mode shipped.","fix":"Say: \"Use only the release notes.\"","checks":["r2"]},{"title":"Calling R3 Yes","why":"Email alerts shipped, but Slack alerts did not.","fix":"Say: \"Partly = some of it shipped.\"","checks":["r1"]},{"title":"Wrong table","why":"The AI adds a notes column.","fix":"Give the exact header; table only.","checks":["r0"]},{"title":"Getting markdown back","why":"AI adds bold and headings by default, which show up as stray symbols where this is pasted.","fix":"Say \"plain text, no bold, no headings, no asterisks\".","checks":["plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting and usually runs long, so a vague \"keep it short\" lands well over the limit.","fix":"Cap each part instead of the total, for example \"each line under 15 words\".","checks":["maxWords"]}],"promptHints":[{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]},{"label":"Sets a length limit","patterns":["\\d+\\s*words","word (limit|count)","under \\d+"]},{"label":"Defines statuses","patterns":["partly","yes","no"]},{"label":"Uses only release notes","patterns":["release notes","not the sales"]}],"hint":"Status mapping needs definitions and a source of truth. State the statuses, the source to trust and the header.","rubricLabels":["The header row is exactly \"Request | Status | Shipped\" with four rows R1 to R4 and nothing outside the table","Statuses are R1 Yes, R2 No, R3 Partly, R4 Partly","Shipped is Oct 20 for R1, - for R2, Nov 2 for R3 and Nov 5 for R4, and dark mode is not marked shipped"]}