Prompt library
Write a weekly status report from raw updates
Outcome-verb discipline converts a diary into a report, and the blocker-must-carry-an-ask rule turns status into an unblocking machine. Committing next week in checkable phrasing builds the accountability loop that makes reports worth writing at all.
Last reviewed July 17, 2026
The prompt
Write my weekly status report from the raw updates below.
Raw updates: {{updates}}
Audience: {{audience}}
Format:
1. Headline: the week in one sentence a skimming executive keeps.
2. Progress: 3-5 bullets. Each states an outcome ("shipped", "closed", "unblocked"), not activity ("worked on", "continued"). Attach a number where one exists.
3. Blocked: what is stuck, who or what unblocks it, and the specific ask. A blocker without an ask is a complaint; sharpen it or cut it.
4. Next week: 2-3 commitments phrased so next week's report can say done or not done.
5. FYI: one line for anything the audience should know but need not act on.
Rules: no activity theater, no "various improvements". If the raw updates are all activity and no outcome, say what is missing instead of dressing it up.Run in idaptOpens a new chat with the prompt prefilled. Nothing sends until you press send.
Fill in the variables
| Variable | What it is | Example |
|---|---|---|
| {{updates}} | Your raw notes, standup lines, commit list | [paste your scattered notes from the week] |
| {{audience}} | Who reads it | my manager and two peer leads |