メニュー
Plan and run a daily standup (daily scrum). Use when structuring a daily standup ritual for an engineering team, product team, or any group that runs daily check-ins.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Plan and run a company or department all-hands meeting. Use when preparing for a quarterly all-hands, town hall, or company-wide meeting where leadership addresses the full organization.
Plan and run a customer meeting — discovery call, demo, business review, or renewal conversation. Use when preparing for any external meeting with a customer, prospect, or client.
Plan and run effective 1:1 meetings between a manager and a direct report (or peer). Use when preparing for a one-on-one, building a recurring 1:1 agenda, or coaching on how to make 1:1s valuable.
Plan and run a recurring team sync (weekly or bi-weekly team meeting). Use when structuring a team standup, weekly sync, or sprint review meeting for an ongoing team.
Plan podcast episodes — structure, talking points, guest prep, show notes, and distribution strategy. Use when the user wants to create a new podcast episode, prepare for a guest interview, or launch a podcast series.
Plan and deliver high-impact presentations to senior executives and decision-makers — C-suite, VPs, boards, steering committees, and investment committees. Use when a user is preparing to present a strategy, project status, budget ask, proposal, or decision brief to people who are time-pressured and focused on business outcomes.
| name | meeting-daily-standup |
| description | Plan and run a daily standup (daily scrum). Use when structuring a daily standup ritual for an engineering team, product team, or any group that runs daily check-ins. |
A daily standup is a synchronization ritual, not a status report. Its job is to:
It is NOT: A place to solve problems, debate architecture, or report to a manager.
| Parameter | Value |
|---|---|
| Duration | 15 minutes — hard cap |
| Frequency | Daily (or 4x/week for async-friendly teams) |
| Time | Same time every day — morning preferred |
| Location | Standing room (in-person) or video call (remote) |
| Attendees | Working team members only; stakeholders observe silently |
Standing up (physically) is the original forcing function for brevity. Remote teams use a visible 15-minute timer instead.
Each person answers:
Hard rules:
Options:
| Method | Best For |
|---|---|
| Round-robin by name | Small teams (< 8); predictable pacing |
| Walk the board (Jira/Kanban) | Larger teams; keeps focus on work, not people |
| Volunteer order | Teams with high trust and discipline |
Walk-the-board is preferred for engineering teams running sprints — you discuss tickets, not individuals.
Any topic that needs > 30 seconds of discussion gets parked:
When someone has a blocker:
Never leave a blocker in standup unassigned. Blockers that aren't assigned get forgotten.
For teams across timezones, async standup via Slack/Discord works well:
Slack workflow or bot (Geekbot, Standuply, etc.):
Async standup template:
✅ Yesterday:
🔄 Today:
🚫 Blocked:
Async standup is NOT a replacement for team connection — still hold a weekly or bi-weekly live sync.
| Anti-Pattern | Why It Hurts | Fix |
|---|---|---|
| Problem-solving during standup | 15 min becomes 45 min | Parking lot + strict offline rule |
| Reporting to the manager | People give the "right" answer, not the real one | Frame standup as peer-to-peer, not upward |
| Skipping "no blockers" | Real blockers get buried in politeness | Require all 3 questions — even "no blockers today" |
| Going through the motions | Team says words but nobody listens | Walk the board instead of round-robin |
| PM / manager "adds context" after every update | Turns peer sync into a briefing | Manager stays silent unless directly asked |
| Standup creep (grows to 30+ min) | Kills morning productivity | Hard timer; merge into weekly sync if needed |
Signs your standup is broken:
Fix options:
For Scrum teams: