Daily Standup Writer

Standups fail in the same two ways every time. Either it's a brain-dump of everything touched — meetings attended, emails sent, tickets opened — which buries the actual signal under noise. Or it's a one-liner ("worked on the project") that tells your manager nothing and prompts a follow-up DM. Neither version answers the question the team actually has: is anything moving, is anything at risk, do I need to help.

The skill takes whatever you've got — messy notes, copy-pasted Slack messages, stream of consciousness — and runs it through the PCB filter. Progress is only what moved a deliverable forward, quantified where possible. Activity that didn't produce an outcome gets stripped. Committed (Today) is specific tasks tied to deliverables, not vague intent. Blockers is the gift section — what you need, who needs to do it, by when, with the @mention so the right person gets pinged. "Blocked on the API" helps nobody; "@devops, blocked on staging credentials, asked Monday, no response" gets you unblocked.

It calibrates to context. Engineering teams get PR references and technical specifics. Cross-functional teams get plain English. Executive-facing standups translate outcomes into business terms — "secured partnership with [vendor]" rather than "had three calls with vendors." There's a dedicated pattern for the days when nothing moved forward (investigation days, firefighting days, all-meetings days) that reframes ruling-out-three-approaches as progress without overselling it. And a two-minute mode — three lines, biggest outcome, top task, blockers — for when you've got 90 seconds before the standup channel posts.

What it won't do: editorialise, hide blockers to look better, or pad activity into fake progress. If yesterday was genuinely a wash, you get an honest update with a clear plan for today, not a creative reframing.