---
name: status-reporting
description: Generate work-item-aware standups and status summaries from current workspace memory, recent logs, and communication evidence.
compatibility: opencode
trigger: always_on
glob: ""
---

## When To Use

Use this skill for standups, daily scrum updates, end-of-day summaries, and short progress reports.

## Workflow

1. Read current state, active work items, recent logs, and latest communication evidence.
2. Use the previous workday as the default source for "Yesterday" style updates.
3. Group updates by work item when possible.
4. If one work item has multiple concrete updates, use one top-level work-item bullet with indented markdown sub-bullets.
5. Exclude side chatter unless it changed work scope, priority, risk, or blockers.

## Output Rules

- Use explicit work-item ID and title when available.
- Keep the report concise and ready to send.
- Do not mention internal evidence sources unless the user asks.
- Use `Blockers: None` only when no blocker is visible in current memory.