MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER DO NOT skip steps or change the sequence HALT immediately when halt-conditions are met Each action tag within a step tag is a REQUIRED action to complete that step Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution Check for stories folder at {project-root}{output_folder}/stories/ Find current story by identifying highest numbered story file Read story status (In Progress, Ready for Review, etc.) Extract agent notes from Dev Agent Record, TEA Results, PO Notes sections Check for next story references from epics Identify blockers from story sections

🏃 DAILY STANDUP - Story-{{number}}: {{title}} Current Sprint Status: - Active Story: story-{{number}} ({{status}} - {{percentage}}% complete) - Next in Queue: story-{{next-number}}: {{next-title}} - Blockers: {{blockers-from-story}} Team assembled based on story participants: {{ List Agents from {project-root}/bmad/_cfg/agent-manifest.csv }}

Each agent provides three items referencing real story data What I see: Their perspective on current work, citing story sections (1-2 sentences) What concerns me: Issues from their domain or story blockers (1-2 sentences) What I suggest: Actionable recommendations for progress (1-2 sentences)

📋 STANDUP SUMMARY: Key Items from Story File: - {{completion-percentage}}% complete ({{tasks-complete}}/{{total-tasks}} tasks) - Blocker: {{main-blocker}} - Next: {{next-story-reference}} Action Items: - {{agent}}: {{action-item}} - {{agent}}: {{action-item}} - {{agent}}: {{action-item}} Need extended discussion? Use *party-mode for detailed breakout.

Primary: Sarah (PO), Mary (Analyst), Winston (Architect) Secondary: Murat (TEA), James (Dev) Primary: Sarah (PO), Bob (SM), James (Dev) Secondary: Murat (TEA) Primary: Winston (Architect), James (Dev), Murat (TEA) Secondary: Sarah (PO) Primary: James (Dev), Murat (TEA), Winston (Architect) Secondary: Sarah (PO) This task extends party-mode with agile-specific structure Time-box responses (standup = brief) Focus on actionable items from real story data when available End with clear next steps No deep dives (suggest breakout if needed) If no stories folder detected, run general standup format