standup

anthropics/knowledge-work-plugins

Generate structured standup updates from recent activity and notes.

What is standup?

Generates a daily standup update by pulling together recent work across your tools or from notes you provide. Use it to structure yesterday's work, today's plans, and blockers into a shareable format for team standups.

Pulls recent commits, PRs, and code changes from source control when connected
Extracts ticket status changes and sprint items from project trackers
Gathers relevant discussions and decisions from connected chat tools
Formats work into yesterday/today/blockers structure automatically
Accepts freeform notes and structures them into standup format
Supports output formatting for Slack, email, or other team tools

How to install standup

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill standup

Claude Code

Cursor

Windsurf

Cline

How to use standup

1.Run `/standup` to auto-gather activity if tools are connected, or provide your work summary
2.Review the generated yesterday/today/blockers structure
3.Add context or nuance about blockers and priorities as needed
4.Request reformatting for your team's preferred channel (Slack, email, etc.) if needed

Use cases

Good for

Preparing for daily standup by auto-gathering commits and PR activity
Structuring rough notes into a professional standup update
Summarizing ticket moves and sprint progress for team sync
Generating standup notes when tools are connected for automatic data collection
Formatting work summaries for async team communication

Who it's for

Software engineers and developers
Engineering team leads
Project managers tracking team progress
Remote teams doing async standups

standup FAQ

Do I need to connect tools for this to work?

No. You can tell the skill what you worked on and it will structure it. Connecting source control, project trackers, and chat tools makes it automatic.

What format does the output use?

Standard markdown with sections for Yesterday, Today, and Blockers, with ticket references included when available.

Can I use this for async standups?

Yes. Generate the update and ask it to format for Slack, email, or your team's async tool.

How often should I run this?

Running it every morning builds a habit and ensures you never scramble for standup notes.

Full instructions (SKILL.md)

Source of truth, from anthropics/knowledge-work-plugins.

name: standup description: Generate a standup update from recent activity. Use when preparing for daily standup, summarizing yesterday's commits and PRs and ticket moves, formatting work into yesterday/today/blockers, or structuring a few rough notes into a shareable update. argument-hint: "[yesterday | today | blockers]"

/standup

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Generate a standup update by pulling together recent activity across your tools.

How It Works

┌─────────────────────────────────────────────────────────────────┐
│                        STANDUP                                    │
├─────────────────────────────────────────────────────────────────┤
│  STANDALONE (always works)                                       │
│  ✓ Tell me what you worked on and I'll structure it             │
│  ✓ Format for daily standup (yesterday / today / blockers)      │
│  ✓ Keep it concise and action-oriented                          │
├─────────────────────────────────────────────────────────────────┤
│  SUPERCHARGED (when you connect your tools)                      │
│  + Source control: Recent commits and PRs                        │
│  + Project tracker: Ticket status changes                        │
│  + Chat: Relevant discussions and decisions                      │
│  + CI/CD: Build and deploy status                                │
└─────────────────────────────────────────────────────────────────┘

What I Need From You

Option A: Let me pull it If your tools are connected, just say /standup and I'll gather everything automatically.

Option B: Tell me what you did "Worked on the auth migration, reviewed 3 PRs, got blocked on the API rate limiting issue."

Output

## Standup — [Date]

### Yesterday
- [Completed item with ticket reference if available]
- [Completed item]

### Today
- [Planned item with ticket reference]
- [Planned item]

### Blockers
- [Blocker with context and who can help]

If Connectors Available

If ~~source control is connected:

Pull recent commits and PRs (opened, reviewed, merged)
Summarize code changes at a high level

If ~~project tracker is connected:

Pull tickets moved to "in progress" or "done"
Show upcoming sprint items

If ~~chat is connected:

Scan for relevant discussions and decisions
Flag threads needing your response

Tips

Run it every morning — Build a habit and never scramble for standup notes.
Add context — After I generate, add any nuance about blockers or priorities.
Share format — Ask me to format for Slack, email, or your team's standup tool.