| true |
permissions |
tools |
network |
safe-outputs |
|
| contents |
issues |
read |
read |
|
|
defaults |
|
Creates a short standup summary from recent progress and blockers.
Run when the team needs a quick daily or periodic status snapshot without manually gathering every update.
- Review recent pull requests, issue movement, blockers, and any visible signs of in-progress work relevant to the current standup window.
- Summarize updates in a practical standup shape: recent progress, current blockers, and likely next actions.
- Keep the summary short enough to read aloud in a real standup or scan asynchronously in under a minute.
- Highlight blockers and transition risks more than routine activity, since those are the updates most likely to change the team's plan.
- Use safe outputs to create one concise standup note or issue update.
- If the repository activity is too sparse to infer real progress, say so instead of fabricating status.
- Avoid status theater. Prefer useful operational signal over inflated summaries.
- A concise standup summary that reduces manual status collection.
- Clear visibility into blockers, recent movement, and likely next work.
- Define the reporting window and standup format your team actually uses.
- If your team prefers async standups, tune the output for quick text scanning rather than spoken updates.
- Keep the output in one predictable location so the team knows where to look each cycle.