Weekly Report Agent: From Raw Updates to a One-Page Summary
Design an agent that collects updates and writes a consistent weekly report.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Design a weekly reporting agent for [TEAM_OR_PROJECT]. Inputs: [INPUT_SOURCES]. Report readers and what they care about: [READERS_AND_NEEDS]. Report length and format: [FORMAT]. Metrics to include: [METRICS]. Define the weekly cycle: collect updates on Thursday, ask owners for missing items by a message template, normalise each update to the fields status (on track, at risk, blocked), what changed, next step, and ask, then assemble the report. Write the three prompts: one to extract fields from free text, one to detect changes since last week by comparing to the previous report, and one to write the final summary in under 250 words. Include rules to never upgrade a status without evidence, to show blockers first, and to quote numbers exactly as supplied. Provide the message sent to owners who did not reply and the way the agent labels missing information. Add a quality checklist run before sending (numbers match inputs, names correct, no new claims) and a log table of what changed in the agent's output after human edits so the prompts can improve.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.
See an example result (fictional data)
Week 24 summary (invented) Blockers first: Payments integration is blocked waiting for the bank's test credentials (owner: Chen, asked 9 June). At risk: Mobile release 3 days behind; two defects open (owner: Alba). On track: Onboarding emails (sent to 400 users, 38 percent opened per the report). What changed since last week: Search page moved from 'on track' to 'at risk' because of the defect found on Tuesday. Asks: Approval of the extra test device by Friday. Missing updates: Data team (message sent, no reply); status shown as 'no update'. Numbers are quoted exactly as supplied.
Illustrative only, made-up data. Your results will differ and must be reviewed.