{"id":"lead-retro-actions-csv","audience":"product-managers","category":"leadership-work","track":"leadership","level":"intermediate","technique":"format","title":"Turn retro notes into a CSV of agreed action items","free":false,"task":"Your tracker imports retro actions from CSV. Output one code block containing a CSV with the header action,owner,due and one row per action the team actually agreed to, with due dates as YYYY-MM-DD. Leave out ideas that weren't agreed. Outside the code block, write nothing or at most one short line.","materialLabel":"Sprint 42 retro notes (attached to your prompt automatically)","material":"Sprint 42 retro - Checkout squad, Thu Nov 6\n\nWent well: payments refactor shipped, zero sev-1s.\nDidn't go well: QA got builds late (Wed afternoon) three sprints running. Design specs changed mid-sprint twice.\n\nAction ideas discussed:\n1. Code freeze Tuesday 5 pm so QA has 2 full days. AGREED, owner Priyanka, start next sprint (Nov 11).\n2. Design spec lock at sprint planning, changes go to next sprint. AGREED, owner Mo, by Nov 10.\n3. Hire a second QA engineer. Raj (eng manager) said no, not in budget. NOT agreed.\n4. Rotate the retro facilitator. AGREED, owner Sam, set up the rotation by Nov 14.\n5. Move stand-up to 10 am. Some liked it, no decision, revisit next retro.\n6. Add a \"late build\" alert to the QA channel. AGREED, owner Priyanka, by Nov 18.\n\nYear is 2025.","rules":[{"type":"codeBlocks","count":1},{"type":"maxCodeLines","max":5},{"type":"maxProseWords","max":20}],"mistakes":[{"title":"Including every idea","why":"The AI turns all six ideas into action items, even the one that was turned down.","fix":"Add: \"Only actions marked AGREED.\"","checks":["r1","maxCodeLines"]},{"title":"Inventing a header","why":"The AI picks its own columns like Task, Assignee, Date, Status.","fix":"Say: \"Header exactly: action,owner,due\"","checks":["r0"]},{"title":"Loose date formats","why":"The AI writes 'Nov 11' or 'next sprint', which won't import.","fix":"Add: \"Dates as YYYY-MM-DD; the year is 2025.\"","checks":["r2"]},{"title":"Explaining the output","why":"The AI wraps the CSV in a paragraph of explanation.","fix":"Add: \"Output only the code block.\"","checks":["codeBlocks","maxProseWords"]}],"promptHints":[{"label":"Asks for CSV","patterns":["csv","code block"]},{"label":"Gives the header","patterns":["action,owner,due","header"]},{"label":"Filters to agreed items","patterns":["agreed","only.{0,20}decided"]},{"label":"Fixes the date format","patterns":["yyyy-mm-dd","iso","date format"]}],"hint":"Imports break on small differences. Give the AI the exact header, the date format and which items count.","rubricLabels":["The CSV header is exactly action,owner,due","Contains exactly the 4 agreed actions (code freeze, spec lock, facilitator rotation, late-build alert) with owners Priyanka, Mo, Sam, Priyanka; no row for the QA hire or the stand-up time","Due dates are in YYYY-MM-DD format with the year 2025 (2025-11-11, 2025-11-10, 2025-11-14, 2025-11-18)"]}