# Daily Standup

> Use when asked for a standup update, status summary, or "what did I do yesterday". Builds the update from actual git and task activity instead of memory.

- Skill: `dkenge123-oss/daily-standup` (Agent Skill)
- Install (CLI): `npx skillmds@latest add dkenge123-oss/daily-standup`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dkenge123-oss/daily-standup/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: dkenge123-oss (https://skillmd.com/u/dkenge123-oss)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/dkenge123-oss/daily-standup

---


# Daily Standup

The best standup update is reconstructed from evidence, not recalled from vibes.

## Protocol

1. **Gather the evidence.** Check, for the relevant window:
   - `git log --all --author=<user> --since=yesterday --oneline` in each active repo
   - Open branches and their state: in review, blocked, in progress
   - Any task tracker items that moved
2. **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.
3. **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
4. **Flag risks early.** If something is going to slip, the standup is where it gets said, not the deadline.
5. **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.