home / skills / supercent-io / skills-template / standup-meeting

standup-meeting skill

/.agent-skills/standup-meeting

This skill facilitates efficient daily standups by guiding time-boxed updates, blockers, and alignment to improve agile team synchronization.

npx playbooks add skill supercent-io/skills-template --skill standup-meeting

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
4.0 KB
---
name: standup-meeting
description: 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.
tags: [standup, daily-scrum, agile, team-sync, blockers]
platforms: [Claude, ChatGPT, Gemini]
---

# Standup Meeting


## When to use this skill

- **매일**: 같은 시간, 같은 장소
- **스프린트 중**: 팀 동기화 필요 시
- **원격 팀**: 비동기 스탠드업

## Instructions

### Step 1: 3 Questions 포맷

```markdown
## Daily Standup Template

**Date**: 2025-01-15
**Time**: 9:30 AM
**Duration**: 15분

### 팀원 A
- **어제 한 일**:
  - 사용자 인증 API 완료 (#123)
  - Code review 2건
- **오늘 할 일**:
  - JWT refresh token 구현 (#124)
  - 단위 테스트 작성
- **블로커**:
  - Redis 설정 문서 필요 (팀원 B에게 도움 요청)

### 팀원 B
- **어제 한 일**:
  - 프론트엔드 폼 validation (#125)
- **오늘 할 일**:
  - 프로필 페이지 UI 구현 (#126)
- **블로커**: 없음

### 팀원 C
- **어제 한 일**:
  - 데이터베이스 마이그레이션 (#127)
  - 성능 테스트
- **오늘 할 일**:
  - 인덱스 최적화 (#128)
- **블로커**:
  - 프로덕션 DB 접근 권한 필요 (긴급)

### Action Items
1. [ ] 팀원 B가 팀원 A에게 Redis 문서 공유 (오늘 10:00)
2. [ ] 팀장이 팀원 C의 DB 권한 요청 (오늘 중)
```

### Step 2: Walking the Board (보드 기반)

```markdown
## Standup: Walking the Board

**Sprint Goal**: 사용자 인증 시스템 완성

### In Progress
- #123: User Login API (팀원 A, 80% 완료)
- #124: Refresh Token (팀원 A, 시작 예정)
- #125: Form Validation (팀원 B, 90% 완료)

### Blocked
- #127: DB Migration (팀원 C)
  - **블로커**: 권한 필요
  - **Owner**: 팀장
  - **ETA**: 오늘 오후

### Ready for Review
- #122: Password Reset (팀원 D)
  - 리뷰어 필요

### Done
- #120: Email Service Integration
- #121: User Registration

### Sprint Progress
- **Completed**: 12 points
- **Remaining**: 13 points
- **On Track**: Yes ✅
```

### Step 3: 비동기 Standup (원격 팀)

**Slack 템플릿**:
```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 회의록

```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권한)

## Individual Updates
[위의 3 Questions 포맷 참조]

## Action Items
1. 팀장: DB 권한 요청 (High priority)
2. 팀원 B: Redis 문서 공유
3. 팀원 D: PR #122 리뷰어 할당

## Notes
- Sprint goal on track
- Team morale: High
```

## Constraints

### 필수 규칙 (MUST)

1. **Time-boxed**: 15분 이내
2. **같은 시간**: 매일 일정한 시간
3. **전원 참여**: 모든 팀원 업데이트

### 금지 사항 (MUST NOT)

1. **Problem Solving**: 스탠드업에서 문제 해결하지 않음
2. **Status Report**: 관리자에게 보고하는 자리 아님
3. **Late Start**: 시간 엄수

## Best practices

1. **Stand Up**: 실제로 서서 진행 (짧게 유지)
2. **Parking Lot**: 깊은 논의는 별도 시간
3. **Visualize**: 보드를 보며 진행

## References

- [Scrum Guide - Daily Scrum](https://scrumguides.org/)
- [15 Minute Stand-up](https://www.mountaingoatsoftware.com/agile/scrum/meetings/daily-scrum)

## Metadata

### 버전
- **현재 버전**: 1.0.0
- **최종 업데이트**: 2025-01-01
- **호환 플랫폼**: Claude, ChatGPT, Gemini

### 태그
`#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 -->

Overview

This skill runs effective daily standup meetings for agile teams, focusing on time-boxed sync, blocker identification, and action-item tracking. It supports in-person, remote asynchronous, and board-driven formats to keep sprints on track. Use it to maintain consistent cadence, surface impediments, and ensure quick follow-up.

How this skill works

The skill guides a three-question format (yesterday, today, blockers), a walking-the-board flow to review work-in-progress and blocked items, and an async template for remote teams. It enforces a 15-minute time box, records attendees and action items, and highlights owners and ETAs for blockers. Outputs concise meeting notes and a prioritized action list.

When to use it

  • Daily morning sync at the same time and place
  • During a sprint to confirm progress toward the sprint goal
  • When remote or distributed teams need asynchronous updates
  • When you need quick blocker escalation and ownership
  • Before planning or demo days to verify readiness

Best practices

  • Keep the meeting under 15 minutes and stand up to reinforce brevity
  • Use the 3-questions format (Yesterday / Today / Blockers) for consistent updates
  • Walk the board: review In Progress, Blocked, Ready for Review, Done
  • Capture clear action items with owners and due times during the meeting
  • Use a parking-lot for deep problem-solving outside the standup

Example use cases

  • In-person daily standup: 15-minute team sync using the board to identify blocked stories
  • Remote async standup: Slack template for team members to post Yesterday/Today/Blockers before a set cutoff
  • Walking-the-board: Product owner and team review sprint progress and update ETA on blocked tasks
  • Blocker escalation: Record blocker, assign owner (e.g., team lead), and set same-day ETA
  • Post-standup follow-up: Convert parking-lot topics into a separate troubleshooting session with required stakeholders

FAQ

How long should each standup be?

Keep the full standup time-boxed to 15 minutes; individual updates should be brief and focused on work and blockers.

What if a blocker needs discussion?

Do not solve it in the standup — add it to the parking-lot and schedule a focused session with relevant participants immediately after.

How do remote teams handle time zones?

Use a consistent daily cutoff for async updates and a shared board; rotate meeting times if live attendance is required to share burden fairly.