standup-meeting
Conduct effective daily standup meetings for agile teams. Use when facilitating standups, tracking blockers, or improving team synchronization. Handles standup format, time management, and blocker resolution.
Best use case
standup-meeting is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Conduct effective daily standup meetings for agile teams. Use when facilitating standups, tracking blockers, or improving team synchronization. Handles standup format, time management, and blocker resolution.
Teams using standup-meeting should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/standup-meeting/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How standup-meeting Compares
| Feature / Agent | standup-meeting | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Conduct effective daily standup meetings for agile teams. Use when facilitating standups, tracking blockers, or improving team synchronization. Handles standup format, time management, and blocker resolution.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Standup Meeting ## When to use this skill - **Daily**: same time, same place - **During a sprint**: when team sync is needed - **Remote teams**: async standup ## Instructions ### Step 1: 3 Questions Format ```markdown ## Daily Standup Template **Date**: 2025-01-15 **Time**: 9:30 AM **Duration**: 15 minutes ### Team Member A - **Yesterday**: - Completed user authentication API (#123) - 2 code reviews - **Today**: - Implement JWT refresh token (#124) - Write unit tests - **Blockers**: - Need Redis setup docs (ask Team Member B for help) ### Team Member B - **Yesterday**: - Frontend form validation (#125) - **Today**: - Implement profile page UI (#126) - **Blockers**: None ### Team Member C - **Yesterday**: - Database migration (#127) - Performance testing - **Today**: - Index optimization (#128) - **Blockers**: - Need production DB access (urgent) ### Action Items 1. [ ] Team Member B shares Redis docs with Team Member A (Today 10:00) 2. [ ] Team lead requests DB access for Team Member C (Today) ``` ### Step 2: Walking the Board (Board-Based) ```markdown ## Standup: Walking the Board **Sprint Goal**: Complete user authentication system ### In Progress - #123: User Login API (Team Member A, 80% done) - #124: Refresh Token (Team Member A, planned) - #125: Form Validation (Team Member B, 90% done) ### Blocked - #127: DB Migration (Team Member C) - **Blocker**: Access needed - **Owner**: Team Lead - **ETA**: This afternoon ### Ready for Review - #122: Password Reset (Team Member D) - Need reviewer ### Done - #120: Email Service Integration - #121: User Registration ### Sprint Progress - **Completed**: 12 points - **Remaining**: 13 points - **On Track**: Yes ✅ ``` ### Step 3: Async Standup (Remote Teams) **Slack template**: ```markdown [Daily Update - 2025-01-15] **Yesterday** - Completed user authentication flow - Fixed bug in password validation **Today** - Implementing JWT refresh tokens - Writing unit tests **Blockers** - None **Sprint Progress** - 8/13 story points completed ``` ## Output format ### Standup Minutes ```markdown # Daily Standup - 2025-01-15 **Attendees**: 5/5 **Duration**: 12 minutes **Sprint**: Sprint 10 (Day 3/10) ## Summary - Stories Completed: 2 (5 points) - Stories In Progress: 3 (8 points) - Blockers: 1 (DB access permission) ## Individual Updates [Refer to the 3 Questions format above] ## Action Items 1. Team lead: Request DB access (High priority) 2. Team Member B: Share Redis docs 3. Team Member D: Assign reviewer for PR #122 ## Notes - Sprint goal on track - Team morale: High ``` ## Constraints ### Required Rules (MUST) 1. **Time-boxed**: within 15 minutes 2. **Same time**: consistent time every day 3. **Everyone participates**: every team member gives an update ### Prohibited (MUST NOT) 1. **Problem Solving**: Do not solve problems in the standup 2. **Status Report**: Not a status report to management 3. **Late Start**: Start on time ## Best practices 1. **Stand Up**: Actually stand up (keep it short) 2. **Parking Lot**: Deep discussion goes to a separate time 3. **Visualize**: Run it while looking at the board ## References - [Scrum Guide - Daily Scrum](https://scrumguides.org/) - [15 Minute Stand-up](https://www.mountaingoatsoftware.com/agile/scrum/meetings/daily-scrum) ## Metadata ### Version - **Current version**: 1.0.0 - **Last updated**: 2025-01-01 - **Supported platforms**: Claude, ChatGPT, Gemini ### Tags `#standup` `#daily-scrum` `#agile` `#team-sync` `#project-management` ## Examples ### Example 1: Basic usage <!-- Add example content here --> ### Example 2: Advanced usage <!-- Add advanced example content here -->
Related Skills
Meeting Briefing Skill
You are a meeting preparation assistant for an in-house legal team. You gather context from connected sources, prepare structured briefings for meetings with legal relevance, and help track action items that arise from meetings.
meeting-scheduler-helper
Meeting Scheduler Helper - Auto-activating skill for Business Automation. Triggers on: meeting scheduler helper, meeting scheduler helper Part of the Business Automation skill category.
meeting-prep
Prepare briefings for today's meetings — attendee research, email history, past meeting notes, LinkedIn, and company context. Use when running the daily meeting prep cron, or when user asks to prepare for meetings, review who they're meeting with, or get context on upcoming calls.
recipe-reschedule-meeting
Move a Google Calendar event to a new time and automatically notify all attendees.
gws-workflow-standup-report
Google Workflow: Today's meetings + open tasks as a standup summary.
gws-workflow-meeting-prep
Google Workflow: Prepare for your next meeting: agenda, attendees, and linked docs.
meeting-minutes
Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.
meeting-minutes-taker
Transforms raw meeting transcripts into high-fidelity, structured meeting minutes with iterative review for completeness. This skill should be used when (1) a meeting transcript is provided and meeting minutes, notes, or summaries are requested, (2) multiple versions of meeting minutes need to be merged without losing content, (3) existing minutes need to be reviewed against the original transcript for missing items, (4) transcript has anonymous speakers like "Speaker 1/2/3" that need identification. Features include: speaker identification via feature analysis (word count, speaking style, topic focus) with context.md team directory mapping, intelligent file naming from content, integration with transcript-fixer for pre-processing, evidence-based recording with speaker quotes, Mermaid diagrams for architecture discussions, multi-turn parallel generation to avoid content loss, and iterative human-in-the-loop refinement.
board-meeting
Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes /cs:board, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.
daily-meeting-update
Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history. Conducts 4-question interview (yesterday, today, blockers, discussion topics) and generates formatted Markdown update.
team-collaboration-standup-notes
You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.
lark-workflow-standup-report
日程待办摘要:编排 calendar +agenda 和 task +get-my-tasks,生成指定日期的日程与未完成任务摘要。适用于了解今天/明天/本周的安排。