Standup Summary

Goal

Convert a team standup transcript into a structured summary that clearly separates blockers, progress updates, and next steps for each team member.

Trigger

After a team standup meeting ends and a transcript or rough notes are available.

Steps

1. 1

   Analyze the standup transcript or notes below: $standup_transcript

   • □Transcript or notes have been pasted in
   • □All team members mentioned are identifiable

   Analyze the standup transcript or notes below:
   
   $standup_transcript

2. 2

   Extract progress updates for each person — what they completed or made meaningful movement on since the last standup. Group by individual contributor.

   • □Every speaker has at least one progress item or is noted as having none
   • □Items are concise and specific, not vague
3. 3

   Identify all blockers raised — anything preventing progress, a dependency on another person or team, or an unresolved question. Note who owns each blocker and who can resolve it if mentioned.

   • □Each blocker is attributed to a person
   • □Resolution owner is noted where known
4. 4

   List next steps for each team member — concrete tasks or intentions they committed to before the next standup. Flag any items that require coordination between multiple people.

   • □Next steps are actionable, not vague intentions
   • □Cross-team dependencies are flagged
5. 5

   Compose the final standup summary with three clearly labeled sections: Progress, Blockers, and Next Steps. Use bullet points grouped by person. Prepend a one-sentence team-level status at the top.

   • □All three sections are present
   • □Team-level status sentence is included
   • □Summary is skimmable in under 60 seconds

Output format

A structured summary with a one-sentence team status at the top, followed by three sections — Progress, Blockers, and Next Steps — each using bullet points grouped by contributor name in bold. Keep the total length under 300 words.