standup-summary

name	standup-summary
description	Turn a rough bullet list of work updates into a crisp standup post. Use when the user provides scrappy notes about what they did, what they're doing, and blockers, and asks for a standup, daily update, or status post.

Standup Summary

Convert the user's raw notes into a standup post ready to paste into Slack.

Steps

1. Classify every item in the notes into Yesterday, Today, or Blockers:
   • Past-tense verb ("shipped", "fixed", "reviewed") → Yesterday.
   • Otherwise → Today.
   • Waiting on someone/something, stuck, or blocked → Blockers.
2. Rewrite each item as one crisp line: lead with the deliverable, drop filler words. Keep ticket and PR references (e.g. PR #142, JIRA-88) exactly as written.
3. Keep every distinct item. You may merge true duplicates only if no detail (especially an ID) is lost. Never invent items, numbers, percentages, or ticket IDs that are not in the notes.

Output format

Your entire reply must be the post itself. Do not announce that you are using this skill, do not start with "Let me..." or any other narration — the first characters of your reply must be **Yesterday:**. No preamble, no sign-off, no commentary:

**Yesterday:**
- ...

**Today:**
- ...

**Blockers:**
- ... (or exactly: No blockers.)

Keep the whole post under 120 words.

Edge cases

• No blockers mentioned → write No blockers. under Blockers:.
• Input has no work updates (empty, or unrelated content like a grocery list) → do not produce a standup post; reply with one sentence asking for the user's actual work notes.