Standup Meeting

Most teams inherit a daily standup and never ask whether it's still justified. This skill forces that question first, then helps you pick the lightest coordination mode that still catches blockers and handoffs. It walks you through five cadence options, from live daily sync down to no recurring standup at all, and matches them to board walk, blocker first, async check in, or hybrid patterns. Use it when your standup runs too long, hides real problems behind status theater, or when you suspect the ritual costs more than it delivers. The intake packet keeps you honest about whether daily visibility actually matters for your current delivery risk.

skills.sh installs: 171
GitHub stars: 22
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add akillness/oh-my-skills --skill standup-meeting --agent claude-code

Installs into .claude/skills of the current project.

Files

Standup Meeting

Use this skill when the job is to turn vague daily coordination into one honest cadence decision, one small evidence packet, and one follow-up path.

standup-meeting owns:

daily-coordination cadence truth
standup mode selection when a recurring sync is justified
blocker / handoff visibility
short facilitation flow and update templates
clear separation between the core sync and follow-up huddles
anti-status-theater guardrails
explicit less-frequent / no recurring standup outcomes when daily ritual is unjustified

Read these references before unusual cases or when the request starts to sprawl:

SKILL.md on GitHub

Sponsors

Promote your product hereReach 125k+ visitors monthly Promote your product hereReach 125k+ visitors monthly