{"id":"pro-pm-thread-scope-update","audience":"product-managers","category":"summarizing","technique":"grounding","title":"Sum up a scope debate thread after the VP's final call","free":false,"task":"You're the PM, and a 30-message thread about cutting scope for the January release finally ended with a call from the VP. Your team wants exactly 3 numbered lines in Slack: what's in, what's cut, and what happens next with the owner, under 60 words, plain text. Use the VP's final call, not earlier proposals, and leave out the arguments. Write a prompt that gets you exactly that.","materialLabel":"The Slack thread (attached to your prompt automatically)","material":"#plateful-jan-release - thread\n\nNina (design): We can't do all 4 features by Jan 15. Proposal: ship meal plans + grocery list, cut pantry tracker and budget view.\nOwen (eng lead): Agree on cutting pantry tracker. Budget view is almost done though, maybe keep it?\nSara (marketing): Marketing already promised budget view in the holiday email 😬\nNina: then cut grocery list instead?\nOwen: grocery list is the #1 request, cutting it would be bad.\nSara: honestly I'd push the date to Feb 1 and ship everything\nNina: Feb 1 conflicts with the partner launch\nOwen: ok what if we ship 3: meal plans, grocery list, budget view. Pantry tracker moves to March.\n(12 more messages arguing about icons and whether \"budget view\" should be called \"spending view\")\nRavi (VP Product): Decision: Jan 15 stays. Ship meal plans, grocery list, and budget view. Pantry tracker moves to the March release. Sara, please update the holiday email so it doesn't promise anything we're not shipping. Owen owns the updated release plan by Friday.\nSara: on it 👍\nOwen: 👍","rules":[{"type":"numberedItems","count":3},{"type":"maxWords","max":60},{"type":"plainText"}],"mistakes":[{"title":"Retelling the debate","why":"The AI walks through every proposal, so the final call gets lost.","fix":"Add: \"Use only the VP's final decision. Skip the debate.\"","checks":["r2"]},{"title":"Not giving the line order","why":"The AI writes a paragraph mixing what's in and out.","fix":"Add: \"Line 1 what ships, line 2 what's cut, line 3 next steps with owners.\"","checks":["r0"]},{"title":"Dropping the owners","why":"The AI writes 'the release plan will be updated' with no name.","fix":"Add: \"Name the owner and deadline for each next step.\"","checks":["r1"]},{"title":"Letting the AI pick the layout","why":"The AI uses bold labels and emoji.","fix":"Be exact: \"Exactly 3 numbered lines, plain text.\"","checks":["numberedItems","plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting. Ask for \"under 60 words\" and it often lands well over.","fix":"Cap each part instead: \"each line under 14 words.\"","checks":["maxWords"]}],"promptHints":[{"label":"Says how many lines","patterns":["\\b(3|three)\\b"]},{"label":"Uses the final call","patterns":["final","vp","ravi","decision"]},{"label":"Gives the line order","patterns":["what'?s in","what'?s cut","next step","line 1"]},{"label":"Names the owners","patterns":["owner","who","owen|sara"]},{"label":"Sets a word limit","patterns":["\\d+\\s*words","word (limit|count)"]}],"hint":"Long threads end with one decision. Tell the AI to report only that call, in a fixed line order, with names on the next steps.","rubricLabels":["Line 1 says what ships Jan 15 (meal plans, grocery list, budget view), line 2 says pantry tracker moves to the March release, line 3 gives next steps with owners","Next steps name Owen for the updated release plan by Friday and Sara for updating the holiday email, and the release date is Jan 15 (not Feb 1)","Leaves out the arguments and rejected proposals (cutting grocery list, pushing to Feb 1, naming debate), with no intro"]}