Standup Summary

Goal

Transform raw standup notes into a structured summary with blockers, progress, and next steps for easy team reference.

Trigger

Invoke after a daily standup meeting when notes or a transcript need to be distilled into a shared summary.

Steps

1. 1

   Analyze the standup notes or transcript provided below: $standup_notes

   • □Raw notes or transcript are present
   • □Content covers at least one team member's update

   Analyze the standup notes or transcript provided below:
   
   $standup_notes

2. 2

   Identify and list all blockers mentioned. For each blocker, note who owns it and what is preventing progress. If no blockers were mentioned, explicitly state 'No blockers reported.'

   • □Every mentioned blocker is captured
   • □Owner is attributed to each blocker
3. 3

   Extract progress updates for each team member. Summarize what was completed or meaningfully advanced since the last standup in one to two sentences per person.

   • □Each speaking team member has a progress entry
   • □Summaries are concise and jargon-free
4. 4

   Compile next steps: list the concrete tasks or goals each team member committed to completing before the next standup. Flag any items that depend on resolving a blocker.

   • □Next steps are specific and actionable
   • □Blocker-dependent tasks are flagged
5. 5

   Write a one-sentence executive summary of the overall team status (e.g., on track, at risk, blocked) suitable for sharing with a manager or stakeholder who did not attend.

   • □Summary reflects the overall tone of the standup
   • □Fits in a single sentence

Output format

Return four labeled sections: 1) Executive Summary — one sentence on overall team status. 2) Blockers — bulleted list with owner names. 3) Progress — bulleted list grouped by team member. 4) Next Steps — bulleted list with owner names and any blocker dependencies noted inline.