Write a weekly status update people actually read.
The template your manager will forward — not because it's polished, because it's useful.
It's Friday afternoon. Slack pings you for the weekly update. Your options are (a) skip it, (b) write a two-line 'still working on the same stuff', or (c) write the update your manager can forward without editing. This is option (c).
THE PROMPT
Write me a weekly status update for my manager. I'll paste bullets of what I did this week below. Structure the update in exactly this format, in Markdown: **Shipped** - One bullet per thing that reached completion. Keep it factual — no "I'm proud to say". **In flight** - One bullet per thing that's mid-progress. Include the specific next step and when it lands. **Blocked or at risk** - One bullet per thing that is stuck or slipping. Name what would unblock it. If nothing is blocked, write "Nothing." — do not manufacture drama. **What I need from you** - Zero to three specific asks of the manager. Each one is a decision, a signoff, or a piece of context, not a status question I could look up myself. No opening greeting. No closing pleasantry. Under 250 words total. If a section has nothing in it, write "Nothing." — do not skip the section. Here's the raw material: [PASTE BULLETS HERE]
**Shipped**
- Cut streaming latency from 1.8s to 400ms on the demo endpoint (Anthropic API config change).
- Landed the /apps page copy and the status page.
- Merged the M3.3 content wave.
**In flight**
- M3.4 content — prompts, help, learn. Landing Monday.
- Playground caps not yet A/B tested for the right free-message count. Deciding by Thursday.
**Blocked or at risk**
- OG image generation for dynamic routes — @vercel/og is on M3.5, blocked on a decision about whether we want image caching.
**What I need from you**
- Signoff on the free-message cap at 3, or a case for 5.
- OK to spend two days in M3.5 on font subsetting even if Lighthouse doesn't strictly demand it.