{"id":"exec-steerco-rag-with-reasons","audience":"project-managers","category":"leadership-work","track":"leadership","technique":"verification","level":"intermediate","title":"Score steering committee workstreams red, amber or green","free":false,"task":"Write the RAG line for each of the 4 workstreams for Thursday's steering committee. Use these rules, not the leads' own colors: Green means on schedule and on budget; Amber means up to 2 weeks late or up to 10% over budget; Red means worse than that. Format exactly 4 numbered lines like \"1. Workstream: Color - reason with the number\". Plain text, nothing else.","materialLabel":"Workstream updates from leads (attached to your prompt automatically)","material":"Project Lumen - workstream updates for SteerCo, Nov 14\n(Budget figures are spend to date vs. plan to date)\n\nData migration - lead: Farah\nSelf-reported status: GREEN\n\"Going well, team is heads down.\" Cutover of customer records was planned for Nov 1; now expected Nov 22. Budget: $210k spent vs $200k planned.\n\nTraining - lead: Benedikt\nSelf-reported status: GREEN\nAll 12 sessions on schedule. Budget: $54k spent vs $50k planned (extra trainer hired).\n\nIntegrations - lead: Yusuf\nSelf-reported status: AMBER\nPayroll interface one week behind the Nov 10 milestone. Budget: $130k spent vs $140k planned.\n\nReporting - lead: Mei\nSelf-reported status: RED\n\"Feels risky.\" Dashboards delivered on Nov 8 as planned. Budget: $75k spent vs $75k planned. Mei is worried the CFO will ask for more dashboards later.\n\nPMO note: SteerCo members said last time they want fewer surprises and to see \"why\" behind each color.","rules":[{"type":"numberedItems","count":4},{"type":"plainText"}],"mistakes":[{"title":"Copying the leads' colors","why":"The AI repeats each lead's self-reported status.","fix":"Say: \"Ignore self-reported colors. Apply my rules to the dates and budget numbers.\"","checks":["r0","r1"]},{"title":"Not giving the thresholds","why":"Without rules the AI judges by tone, so a worried lead becomes Red.","fix":"Give the rules: \"Green on time and budget; Amber up to 2 weeks late or 10% over; Red worse.\"","checks":["r1"]},{"title":"Reasons with no numbers","why":"The AI writes \"slightly delayed\" instead of the actual slip.","fix":"Add: \"Each reason states the number: weeks late or percent over.\"","checks":["r2"]},{"title":"Not showing the line format","why":"The AI writes a formatted status report with headings and paragraphs.","fix":"Show it: \"Format: 1. Workstream: Color - reason. Exactly 4 lines, plain text.\"","checks":["numberedItems","plainText"]}],"promptHints":[{"label":"Gives the color rules","patterns":["2 weeks","10\\s*%","threshold","rules"]},{"label":"Ignores self-reported colors","patterns":["ignore","self.?report","not the leads","their own"]},{"label":"Asks for numbers in each reason","patterns":["number","percent","weeks late","%"]},{"label":"Shows the line format","patterns":["\\b1\\.","format","each line"]},{"label":"Asks for plain text","patterns":["plain","no bold","no markdown"]}],"hint":"Leads grade their own work optimistically or by mood. Give the AI your thresholds and tell it to check the numbers itself.","rubricLabels":["Data migration is Red (3 weeks late, Nov 1 to Nov 22), not Green","Training is Amber (8% over budget, $54k vs $50k), Integrations is Amber (1 week late), and Reporting is Green (on time and on budget)","Each line gives its reason with the actual number (weeks late or percent or dollars over), not just a description"]}