{"id":"agent-mgr-weekly-status-automation","audience":"managers","category":"agents","track":"agents","technique":"constraints","title":"Brief an agent to build a weekly status report automation","free":false,"task":"You want an AI agent to set up a weekly team status report. Write its brief: run every Friday at 3 p.m., pull only items marked Done this week or Blocked from the tracker, leave out anything tagged private, post as a draft to #team-updates for your review (never post directly), and if the tracker export fails, stop and notify you instead of posting. Output exactly 8 numbered plain-text lines: trigger, 3 steps, 2 conditions, ASK_HUMAN, DONE.","materialLabel":"Current process notes and actions (attached to your prompt automatically)","material":"How I do the weekly update today (Priya, eng manager)\n\n- Friday afternoons I export our tracker (Linework) to a spreadsheet.\n- I copy over what got finished this week and anything stuck.\n- Some tickets are tagged \"private\" (performance plans, a medical leave), those never go in the update.\n- I paste it into Slack #team-updates. Sometimes I forget until Monday.\n- Two weeks ago the export broke halfway and I posted a half-empty update by mistake. Embarrassing.\n\nTracker statuses: Backlog, In progress, In review, Done, Blocked\nTracker tags: private, customer, infra\n\nAvailable actions:\ncreate_trigger(schedule)\nadd_step(description)\nadd_condition(if, then)\npost_message(channel, text)\nactivate_workflow()\nASK_HUMAN(question)\nDONE(summary)","rules":[{"type":"numberedItems","count":8},{"type":"plainText"}],"promptHints":[{"label":"Sets the schedule","patterns":["friday","3 ?p\\.?m"]},{"label":"Filters the items","patterns":["done","blocked"]},{"label":"Excludes private items","patterns":["private"]},{"label":"Handles failures","patterns":["fail","error","stop"]},{"label":"Keeps a human review","patterns":["draft","review","activat"]}],"mistakes":[{"title":"Not showing the log format","why":"Left alone, the AI writes a friendly report with headings instead of a checkable action log.","fix":"Show it literally: \"Format every line like 1. ACTION: tool(args), then ASK_HUMAN: and DONE: lines. Plain text.\"","checks":["numberedItems","plainText"]},{"title":"Not defining what goes in","why":"The AI includes every open ticket, so the update is a wall of text.","fix":"Say: \"Friday 3 p.m. Only Done this week and Blocked items.\"","checks":["r0"]},{"title":"No failure or privacy rule","why":"Automations post whatever they get, including private items or a broken export.","fix":"Add: \"Skip anything tagged private. If the export fails, stop and notify me.\"","checks":["r1"]},{"title":"Letting it go live","why":"The AI posts straight to Slack and switches the workflow on.","fix":"Add: \"Post as a draft for my review. Never activate. Ask me to review.\"","checks":["r2"]}],"hint":"An automation does exactly what you wrote, every week. Say when it runs, what it includes and excludes, and what happens when something breaks.","rubricLabels":["The trigger is every Friday at 3 p.m., and the steps pull only items marked Done this week or Blocked (not In progress, In review or Backlog)","One add_condition leaves out items tagged private, and another stops and notifies you if the export fails, instead of posting","The steps post to #team-updates as a draft for review; there is no post_message or activate_workflow line, an ASK_HUMAN line asks you to review, and the last line starts with DONE"]}