Standup

---
name: standup
description: Generate a daily standup digest with progress, blockers, and sprint health
argument-hint: "[project]"
allowed-tools: mcp__rewelo__ticket_list, mcp__rewelo__event_log, mcp__rewelo__report_times, mcp__rewelo__report_summary, mcp__rewelo__calc_priority, mcp__rewelo__tag_list
---

# Daily Standup Digest

Generate a standup summary for project **$0**.

## Data collection

1. Use `ticket_list` with `tags` to get the tickets in each state, e.g. `tags: ["state:wip"]`: its items don't list tags. It returns 100 tickets per call: page with `offset` until you have `total` of them
2. Use `event_log` with `since` (oldest first, 50 events per call: pass the last event's `sequence` as `after` for the next page, until a page is shorter than `limit`) for the transitions and when they happened: `tag_added` events with prefix `state` (value `done` in the last 24 hours for Done; the time a ticket got `state:wip` for how long it has been in progress)
3. Use `report_times` for the cycle times of done tickets

## Sections

### Done (since last standup)
Tickets that transitioned to `state:done` in the last 24 hours.
Show: title, cycle time, priority score.

### In Progress
Tickets currently tagged `state:wip`.
Show: title, how long in WIP, priority score.
Flag any ticket in WIP for more than 3 days.

### Blocked
Tickets tagged `state:blocked` (if tag exists).
Show: title, how long blocked, priority score.

### Up Next
Top 3 open tickets by priority that would fit remaining capacity: `ticket_list` with `excludeTags: ["state:wip", "state:done", "state:blocked"]` and `sort: "priority"`. Open is as plan-sprint has it: a ticket without a state tag is in the backlog too, as new tickets have none until someone tags them.

## Sprint Health (if applicable)

If tickets carry a sprint tag (e.g. `sprint:2026-w39`, as plan-sprint assigns), for the current sprint:
- Total sprint tickets vs. completed (those also tagged `state:done`)
- Priority-weighted progress: sum of (priority * done) / sum of priority for all sprint tickets
- Projected completion based on current throughput

## Output format

Keep it concise — this is a standup, not a report:

```
## Standup — Project Alpha — 2024-01-15

### Done (2)
- Login page redesign (3.2 priority, 2d cycle time)
- Fix password reset bug (4.1 priority, 0.5d cycle time)

### In Progress (3)
- Checkout flow (1.8 priority, 1d in WIP)
- API rate limiting (2.5 priority, 4d in WIP) ⚠️
- User dashboard (1.2 priority, 1d in WIP)

### Up Next
- Email notifications (3.0 priority, cost: 5)
- Export to CSV (2.1 priority, cost: 3)

### Sprint: 5/12 done (42%) | 60% by priority-weight
```