ai-standup

# Standup ## Purpose Generate standup notes from actual PR and commit activity. Produces concise, copy-paste-ready summaries grouped by status. Eliminates manual standup preparation. ## Trigger - Command: `/ai-standup` - Context: preparing for daily standup, team sync, or async status update. ## When to Use - Before daily standup meetings - Async status updates for Slack/Teams channels - End-of-day summaries - Handoff notes between sessions ## When NOT to Use - **Sprint-level summaries** -- use `/ai-sprint retro` - **Incident timelines** -- use `/ai-postmortem` ## Pre-conditions (MANDATORY) 1. Read `.ai-engineering/manifest.yml` — `work_items` section. 2. Read `.ai-engineering/reference/gather-activity-data.md` for the canonical git log, PR query, and work item commands. 3. Use the active provider to gather work item data and include status in standup notes when available. ## Workflow 1. **Determine lookback** -- default: 1 working day. Override with `--days N`. Skip weekends unless `--days` explicitly covers them. 2. **Collect activity** -- use the commands from `.ai-engineering/reference/gather-activity-data.md` to scan: a. Local commits (git log with author filter) b. PRs (provider-specific query) c. Active spec tasks from `.ai-engineering/specs/spec.md` and `.ai-engineering/specs/plan.md` -- current work 3. **Classify items** into three groups: | Group | Criteria | |-------|----------| | **Shipped** | Merged PRs, completed spec tasks | ...