meeting-daily-standup

Plan and structure daily standup meetings for engineering and product teams.

3|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/gilinachum/youtube-storyteller --skill meeting-daily-standup-gilinachum
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meeting-daily-standup
Source: https://github.com/gilinachum/youtube-storyteller/tree/main/agent/knowledge/meeting-daily-standup
Command: npx skills add https://github.com/gilinachum/youtube-storyteller --skill meeting-daily-standup-gilinachum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Daily standups often drift into long status reports, problem-solving sessions, or manager briefings that waste the team's morning. This Skill provides a structured playbook for running a focused 15-minute daily standup that surfaces blockers and aligns the team without derailing into discussion. ## Core Features & Use Cases - Standup Format Design: Defines duration, frequency, attendee rules, and the three-question structure (yesterday, today, blockers) with hard time limits per person. - Facilitation Playbooks: Covers update ordering methods (round-robin, walk-the-board, volunteer), parking lot rules, and blocker assignment protocols. - Async & Remote Variants: Provides Slack-based async standup templates for distributed teams across timezones, plus guidance on when live syncs are still needed. - Anti-Pattern Detection: Lists common failure modes (standup creep, reporting-to-manager, skipped blockers) with concrete fixes, including Israeli/Hebrew team context. - Use Case: A scrum master notices standups regularly run 30 minutes with no blockers ever raised. Use this Skill to diagnose the anti-patterns and restructure the ritual around walk-the-board updates and a strict parking lot. ## Quick Start Help me design a 15-minute daily standup format for my remote engineering team of eight people spread across three timezones.

Frequently Asked Questions about meeting-daily-standup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an effective daily standup meeting?▼

Cap the standup at 15 minutes with each person answering three questions: what they completed yesterday, what they will do today, and what is blocking them. Keep updates to 60-90 seconds per person and park any topic needing more than 30 seconds of discussion for after the meeting.

How to run a daily standup for remote teams across timezones?▼

Use an async standup via Slack or a bot like Geekbot that posts the three questions at each person's local morning and collects answers in a shared channel. Async standup should still be paired with a weekly or bi-weekly live sync to maintain team connection.

What is the difference between round-robin and walk-the-board standups?▼

Round-robin goes person by person and suits small teams under eight people. Walk-the-board reviews tickets on a Jira or Kanban board instead, keeping focus on the work rather than individuals, and is preferred for engineering teams running sprints.

Why does my daily standup keep running over 15 minutes?▼

Standups run long when problem-solving happens during the meeting or updates lack time limits. Use a visible timer, start on time without waiting for latecomers, and enforce a parking lot where any topic needing extended discussion is handled after standup with only relevant people.

What are common daily standup anti-patterns?▼

Common anti-patterns include solving problems during the meeting, treating it as a report to the manager, skipping the blockers question, and managers adding commentary after every update. Fixes include strict offline rules, peer-to-peer framing, and requiring all three questions even when the answer is no blockers.

When should a team change its standup format?▼

Change the format when people give identical updates daily, no blockers are ever raised, attendees disengage, or the meeting consistently exceeds 20 minutes. Options include switching to walk-the-board, moving to async-first with optional live check-ins, or splitting into sub-team standups.