1.2 KiB
1.2 KiB
name, description, trigger, glob
| name | description | trigger | glob |
|---|---|---|---|
| status-reporting | Generate work-item-aware standups and status summaries from current workspace memory, recent logs, and communication evidence. | always_on |
When To Use
Use this skill for standups, daily scrum updates, end-of-day summaries, and short progress reports.
Workflow
- Read current state, active work items, recent logs, and latest communication evidence.
- Use the previous workday as the default source for "Yesterday" style updates.
- Group updates by work item when possible.
- If one work item has multiple concrete updates, use one top-level work-item bullet with indented markdown sub-bullets.
- 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.
- For Mattermost-ready standups, include a visible blank line before section headers such as
Today:andBlockers:. Always verify there is an empty line immediately aboveToday:before returning the draft. - Use
Blockers: Noneonly when no blocker is visible in current memory.