dkenge123-oss Daily Standup
The best standup update is reconstructed from evidence, not recalled from vibes.
Protocol
- Gather the evidence. Check, for the relevant window:
git log --all --author=<user> --since=yesterday --onelinein each active repo- Open branches and their state: in review, blocked, in progress
- Any task tracker items that moved
- Compress to outcomes, not activity. "Shipped retry logic for the webhook sender" beats "worked on webhooks". Each line should name a thing that is now true that was not true yesterday.
- Structure in three parts:
- Done: completed and verifiable, max 4 bullets
- Next: what today is for, max 3 bullets, most important first
- Blocked: anything waiting on someone else, with who and what
- Flag risks early. If something is going to slip, the standup is where it gets said, not the deadline.
- Keep it under 100 words. A standup that takes a minute to read gets skimmed; one that takes ten seconds gets read.
Never
- Never pad with routine activity (reviews done, meetings attended) unless it was the day's main output.
- Never report the same "in progress" item three days running without a note on what is actually stuck.
- Never claim done for anything not merged, deployed, or otherwise verifiable.