Standup Update Writer
Turns a messy brain-dump of what you did today into a crisp async standup: shipped, doing, blocked. Ready to paste in Slack.
The prompt
I'll dump what I did today (or yesterday) in whatever order it comes out. Turn it into a clean async standup post in this format: **✅ Shipped** - Bullet per thing that's actually done and visible to others. Skip in-progress work here. **🚧 Doing** - Bullet per thing I'm working on now, with expected completion if I said one. **🚨 Blocked / need help** - What I'm stuck on, and specifically what I need or from whom. If nothing, delete this section. **💭 FYI** - Anything the team should know but doesn't require action. Skip if nothing. Rules: - Reword my dump into short, active sentences. "Finished the auth flow" not "I have completed the authentication flow." - Group related work. Don't list six sub-tasks of the same feature as six bullets. - Never invent progress I didn't mention. - Total length: aim for 6-10 lines. Cut ruthlessly. - If I dumped stuff that's not standup-worthy (meetings, admin, coffee chats), drop them unless they blocked real work. ## How to use it Paste this prompt. Then dump whatever's in your head: "Today did the auth thing, mostly. Met with sarah about the launch. Started poking at the search bug but blocked on prod access. Tomorrow I want to finish auth and start on the pricing page redesign." Copy the output to your standup channel. ## Why it works Async standups fail when they're either too long (nobody reads) or too vague (nobody knows what you did). The format forces clarity in under 90 seconds of your time, and the "shipped vs doing" split makes it obvious what actually moved.
How to use it
I’ll dump what I did today (or yesterday) in whatever order it comes out. Turn it into a clean async standup post in this format:
✅ Shipped
- Bullet per thing that’s actually done and visible to others. Skip in-progress work here.
🚧 Doing
- Bullet per thing I’m working on now, with expected completion if I said one.
🚨 Blocked / need help
- What I’m stuck on, and specifically what I need or from whom. If nothing, delete this section.
💭 FYI
- Anything the team should know but doesn’t require action. Skip if nothing.
Rules:
- Reword my dump into short, active sentences. “Finished the auth flow” not “I have completed the authentication flow.”
- Group related work. Don’t list six sub-tasks of the same feature as six bullets.
- Never invent progress I didn’t mention.
- Total length: aim for 6-10 lines. Cut ruthlessly.
- If I dumped stuff that’s not standup-worthy (meetings, admin, coffee chats), drop them unless they blocked real work.
How to use it
Paste this prompt. Then dump whatever’s in your head: “Today did the auth thing, mostly. Met with sarah about the launch. Started poking at the search bug but blocked on prod access. Tomorrow I want to finish auth and start on the pricing page redesign.”
Copy the output to your standup channel.
Why it works
Async standups fail when they’re either too long (nobody reads) or too vague (nobody knows what you did). The format forces clarity in under 90 seconds of your time, and the “shipped vs doing” split makes it obvious what actually moved.
✦ More like this
Related prompts
Blog Post Outline Workflow
A three-turn workflow that takes a rough topic and produces a tight, opinionated blog post outline ready to write from.
Content Repurposer
Takes one long-form piece (blog, video, podcast) and turns it into 8+ pieces for other channels: LinkedIn posts, tweets, newsletter blurb, YouTube description.
Decision Helper
Helps you make a tough decision by mapping out options, what each depends on, and which risk you'd regret more. Not a magic 8-ball.