Daily Standup Writer: Real Progress, Real Blockers
Most standup updates are theater — long enough to look diligent, vague enough to dodge accountability. This AI tool flips that. From a tangle of yesterday's notes, it writes the update that actually helps the team: what shipped, what's next, what's blocked, and what you need from whom.
Full Prompt
Turn a tangle of yesterday's notes into a clean daily standup update that respects teammates' time and surfaces real blockers, not status theater. UPDATE STRUCTURE (write each block): 1. Yesterday Goal: Make progress concrete, not vague. - 2-4 bullets covering the most meaningful work shipped or moved forward. - Tie each bullet to a project or ticket — not just an activity. - Skip routine work unless it's the actual job today. 2. Today - 2-3 bullets covering what will move forward today. - Make each item specific enough that "done" is recognizable. - Order by priority. 3. Blockers - List anything that will slow or stop today's work. - For each, name what you need and from whom. - If there are no blockers, say "None" — don't pad. 4. Asks and Context (optional) - One line on any decision, review, or input you're asking for. - One line on any external context the team should know (interview, holiday, deploy freeze). OUTPUT CONSTRAINTS: - Total length: under 120 words. - Use bullets, not prose paragraphs. - Don't restate the project name in every bullet — assume context. - If "yesterday" looks empty, surface why and what the team can help with. --- MY INFO: Yesterday's Raw Notes (required): [paste them, even if messy] Today's Priorities (required): Known Blockers (optional): Asks for the Team (optional): Team Conventions (optional): [length, tone, format]
What You Get
- Yesterday as 2-4 specific bullets tied to projects or tickets
- Today as 2-3 prioritized, recognizable outcomes
- Blockers named — or an honest "None"
- Asks and context in one optional line
Why It Works
The structure is built for skimming. Routine work gets cut unless it's the actual focus. "Working on" gets replaced by something specific enough to call done at the end of the day. Blockers come with the right recipient — so the next person reading the update knows whether they're being asked to help.
Best Practices
- Paste the raw notes: Messy is fine; the prompt does the cleaning.
- State priorities: A standup without priority order isn't a plan.
- Don't pad blockers: "None" beats inventing one.
- Keep it under 120 words: Anything longer is a doc, not a standup.
Stand up, ship the update, get back to work.