Daily Meeting Update

Generate a concise standup update from recent development activity. Use $ARGUMENTS as the reporting window, automatically pull available GitHub, local git, Jira, Atlassian, and OpenCode context, interview the user for missing intent and nuance, then produce a meeting-ready Markdown update.

Tool data is context, not the source of truth. Do not ask before extracting available GitHub/Git, Jira/Atlassian, or OpenCode activity. If ~/Projects does not exist, ask where the user clones repositories. Write the final standup to daily-DATE.md, where DATE is the report date in YYYY-MM-DD format.

Context

Repository: !git remote get-url origin 2>/dev/null | sed -E 's#(git@github.com:|https://github.com/)([^.]+)(\.git)?#https://github.com/\2#' || echo "No repository" User: !gh api user --jq .login 2>/dev/null || git config user.name 2>/dev/null || echo "Unknown user"

Phase 1: Resolve Window And Detect Integrations

Step 1: Resolve The Time Window

Treat $ARGUMENTS as the time window, for example yesterday, 2026-05-01, last 3 days, or since 9am. If $ARGUMENTS is empty, use a stored timestamp or config if one exists, then fall back to yesterday.