meta-report-standup-weeklylisted

# Standup report — spoken, punchy, mechanically sourced The output is a **script to read out loud in about 45 seconds**, not a document. If a line sounds written, it is wrong. Two failure modes this skill exists to prevent, in order of how often they happen: 1. **Asking Simon what he did.** Everything is in git, `gh` and Linear. Asking wastes the one thing he is short of on a Monday morning. 2. **Reading out commits.** Eighty commits become twelve bullets. Nobody in the room wants the log. ## 1. Fix the window, and say what you fixed it to Take today's date from the session context. Never shell out for it. - **Default:** previous Monday 00:00 through now. That is the Monday-standup window. - If he names one ("since Friday", a date range), use his. - If today is not a Monday, the default becomes "since the previous working day" and you say which you assumed in one line before the report. ## 2. Gather from three sources, in parallel, never from him Run all three in one batch. Each is cheap and they do not depend on each other. **Commits.** Simon runs several Conductor worktrees off one object store, so `--all` from any worktree sees every branch he touched: ```bash git log --all --author="$(git config user.email)" --since=<start> \ --date=short --pretty='%ad %h %s' ``` Resolve the author from `git config user.email`, falling back to `user.name` or the GitHub username. **An empty result almost always means the author filter missed, not that he did nothing** — v