How this command is triggered — by the user, by Claude, or both
Slash command
/engineering:standup [yesterday | today | blockers]The summary Claude sees in its command listing — used to decide when to auto-load this command
# /standup > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS.md). Generate a standup update by pulling together recent activity across your tools. ## How It Works ## What I Need From You **Option A: Let me pull it** If your tools are connected, just say `/standup` and I'll gather everything automatically. **Option B: Tell me what you did** "Worked on the auth migration, reviewed 3 PRs, got blocked on the API rate limiting issue." ## Output ## If Connectors Available If **~~source control** is connected: - Pull rec...
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Generate a standup update by pulling together recent activity across your tools.
┌─────────────────────────────────────────────────────────────────┐
│ STANDUP │
├─────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ Tell me what you worked on and I'll structure it │
│ ✓ Format for daily standup (yesterday / today / blockers) │
│ ✓ Keep it concise and action-oriented │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + Source control: Recent commits and PRs │
│ + Project tracker: Ticket status changes │
│ + Chat: Relevant discussions and decisions │
│ + CI/CD: Build and deploy status │
└─────────────────────────────────────────────────────────────────┘
Option A: Let me pull it
If your tools are connected, just say /standup and I'll gather everything automatically.
Option B: Tell me what you did "Worked on the auth migration, reviewed 3 PRs, got blocked on the API rate limiting issue."
## Standup — [Date]
### Yesterday
- [Completed item with ticket reference if available]
- [Completed item]
### Today
- [Planned item with ticket reference]
- [Planned item]
### Blockers
- [Blocker with context and who can help]
If ~~source control is connected:
If ~~project tracker is connected:
If ~~chat is connected:
npx claudepluginhub p/worldlyjohn-engineering-engineering4plugins reuse this command
First indexed Mar 26, 2026
/standupGenerates a daily standup report from your recent Slack messages, categorizing activity into Done, Doing, and Blockers for review and optional posting.
/standupGenerates a daily standup report by scanning recent Slack messages, categorizing them into done/doing/blockers, and presenting the result for review.
/standupGenerates brief operational standup report: task counts, 2-3 key in-progress items, blockers, progress signal, and next recommended command from project state files.
/standupSummarize your recent git commits into a personal standup or weekly recap, scoped to your author identity. Supports custom time windows, author override, and multi-repo scanning.
/standupGenerates standup notes from recent git commits by current user, categorizing into features/fixes/refactors, noting uncommitted work/stashes/blockers over optional timeframe.