anthropics/knowledge-work-plugins

standup

Generate a standup update from recent activity.

Quelltext ansehen
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

/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

markdown
## 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

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

Weitere Skills

Alle Skills
anthropics
Offiziell

customer-escalation

Package an escalation for engineering, product, or leadership with full context. Use when a bug needs engineering attention beyond normal support, multiple customers report the same issue, a customer is threatening to churn, or an issue has sat unresolved past its SLA.

Installationen
2
GitHub Stars
23.921
Aktualisiert
5. Sept.
anthropics
Offiziell

design-critique

Get structured design feedback on usability, hierarchy, and consistency. Trigger with "review this design", "critique this mockup", "what do you think of this screen?", or when sharing a Figma link or screenshot for feedback at any stage from exploration to final polish.

Installationen
2
GitHub Stars
23.921
Aktualisiert
5. Sept.
anthropics
Offiziell

draft-response

Draft a professional customer-facing response tailored to the situation and relationship. Use when answering a product question, responding to an escalation or outage, delivering bad news like a delay or won't-fix, declining a feature request, or replying to a billing issue.

Installationen
2
GitHub Stars
23.921
Aktualisiert
5. Sept.
anthropics
Offiziell

interview-prep

Create structured interview plans with competency-based questions and scorecards. Trigger with "interview plan for", "interview questions for", "how should we interview", "scorecard for", or when the user is preparing to interview candidates.

Installationen
2
GitHub Stars
23.921
Aktualisiert
5. Sept.