standup

Standup

Answer "what did I do" from the ledger instead of memory. The engine returns the facts for the window; render them as bullets a person would actually read out in standup — short, concrete, artifact-linked.

"${CLAUDE_PLUGIN_ROOT}/bin/waybill" mine --all      # catch-up metering first, always
"${CLAUDE_PLUGIN_ROOT}/bin/waybill" query standup [--date yesterday|today|YYYY-MM-DD] \
    [--days <n>] [--from <iso> --to <iso>]

Resolve the window

• Default (no window words): --date yesterday.
• Monday standup: "yesterday" would miss the weekend. --days <n> covers the last n days ending today, so use --days 4 (Friday through today) — or explicit --from <Friday> --to <Sunday> to exclude today. Always say which days the digest covers, from the returned .data.window.
• "this week" / "weekly digest": --days 7.
• A named day ("what did I do Tuesday"): --date <YYYY-MM-DD>.
• Day math is local-calendar (the engine's --date/--days handle it); pass explicit --from/--to only for odd ranges.

Render (bullets, in this order)

Work from the returned .data:

1. Shipped (.data.shipped) — one bullet per item: KEY — title (points, PR links). These are the strongest lines; lead with them.
2. In progress (.data.progressed) — items with metered spend that did not ship in the window: KEY — title (n sessions). Rows with shipped_earlier: true are follow-up on an already-shipped item — say "follow-up on KEY", not "in progress". Mention token counts only if the user asks or the audience is themselves — teammates want the work, not the meter.
3. Started (.data.opened) — newly opened entries, with "estimate pre-registered" noted where true.
4. Blockers / attention — only from .data.attention: open attribution-inbox items or a notable unattributed share are ledger blockers; real work blockers the user must add themselves (ask if a "blockers" line is wanted, don't invent one).