Generate Daily Standup Meeting Templates
A skill that generates ready-to-use daily standup templates and facilitation guidance for agile teams, remote or in person.
Why it matters
Streamline your team's daily standup meetings by generating customized templates. This asset adapts to various agile methodologies and team needs, ensuring efficient communication and progress tracking.
Outcomes
What it gets done
Generate standard daily standup templates.
Create specialized templates for bug triage or release weeks.
Adapt templates for remote or distributed teams.
Incorporate best practices for time management and facilitation.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-daily-standup-template | bash Overview
Daily Standup Template Generator агент
This skill produces ready-to-use daily standup templates - standard, walking-the-board, remote, bug-triage, and release-week variants - plus a facilitation playbook covering timing, common mistakes, and a weekly retrospective format. Use it when setting up or refreshing a team's standup format, especially for remote teams, bug-triage cycles, or release weeks that need a specialized structure.
What it does
This skill designs and facilitates daily standup meetings, grounded in three pillars: transparency (clear, honest updates without spin), inspection (regular check-ins on progress and blockers), and adaptation (fast changes based on new information). It enforces time management - a 15-minute cap for teams up to 9 people, with 1-2 extra minutes per additional participant, strict start and end times regardless of attendance, and a 1-2 minute time box per person. It produces a standard round-robin template covering three questions (what was completed yesterday, what's planned today, and current blockers or impediments), plus action items with an owner and due date, and sprint progress tracking (sprint goal, days remaining, burndown status). It also offers advanced format variations: a "walking the board" template that reviews columns right to left (Done, In Progress, To Do, Blocked), a remote-team edition with async pre-meeting updates plus a synchronous 10-minute discussion and a parking lot for longer topics, a bug-triage-focused format tracking P0/P1 issues alongside daily bug-opened and bug-closed counts, and a release-week format with a readiness checklist and risk assessment.
### Daily Standup - [Date]
**Duration:** 15 minutes | **Start:** [Time] | **Facilitator:** [Name]
### Attendees
- [ ] Team Member 1
- [ ] Team Member 2
- [ ] Team Member 3
### Round Robin Updates
Each person answers:
### 1. What did you complete yesterday?
- Focus on **done** items that move toward sprint goal
- Mention any completed blockers
### 2. What will you work on today?
- Maximum 2-3 items
- Highlight dependencies on others
### 3. What blockers or impediments do you have?
- Anything preventing progress
- Items needing help from others
- Technical or process obstacles
### Action Items
- [ ] [Action] - Owner: [Name] - Due: [Date]
- [ ] [Action] - Owner: [Name] - Due: [Date]
### Sprint Progress
- **Sprint Goal:** [Current sprint objective]
- **Days Remaining:** [X]
- **Burndown Status:** [On track/Behind/Ahead]
When to use - and when NOT to
Use it to design or run daily standups for agile teams, including remote, bug-triage-heavy, or release-week contexts that need a specialized format. It is not meant for status reporting to management or for technical deep-dives - those should be pushed to a parking lot and handled in separate sessions, and updates should stay forward-looking rather than dwelling on the past.
Inputs and outputs
Input is the team's context - size, distribution, and project phase. Output is a ready-to-use standup template plus a full facilitation playbook: how to open in about a minute (state the sprint goal and remaining days, surface urgent announcements, confirm who is present or absent), run updates for 10-12 minutes in a consistent order such as alphabetical or clockwise while capturing action items and blockers, and close in 2-3 minutes by summarizing key blockers and owners and confirming next steps. It also includes facilitation techniques for staying on topic (a parking lot for detailed discussions, polite redirects like "let's discuss that separately," clarifying questions like "how can we help?"), for encouraging participation (weekly-rotating facilitation, direct questions to quiet participants, psychological safety for raising blockers, async updates for introverted team members), a list of common mistakes to avoid (turning it into a status report to a manager, technical deep-dives, past-focused updates, vague commitments, and skipping people who say they have "nothing to share"), and a weekly retrospective template tracking what's working, what could improve, one action for next week, average and longest meeting duration, and participation rate.
Integrations
The skill recommends integrating the template with existing team tools such as Jira and Trello, adapting language and format to the team's culture (formal versus informal), accounting for timezones on distributed teams, and reviewing and updating the template monthly based on team feedback.
Who it's for
Scrum masters, team leads, and agile coaches who need a customizable, ready-to-use standup format and facilitation playbook for teams of varying size, distribution, and project phase.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.