standup
$
npx mdskill add anthropics/knowledge-work-plugins/standupGenerates structured daily standup updates from recent activity or tool integrations for concise team sharing.
- Helps prepare for daily standups by summarizing work and organizing notes.
- Integrates with source control, project trackers, chat, and CI/CD tools when connected.
- Pulls together recent commits, PRs, ticket moves, and discussions to compile updates.
- Formats results into yesterday, today, and blockers sections for easy sharing.
SKILL.md
.github/skills/standupView on GitHub ↗
--- 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](../../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.
More from anthropics/knowledge-work-plugins
- accessibility-reviewRun a WCAG 2.1 AA accessibility audit on a design or page. Trigger with "audit accessibility", "check a11y", "is this accessible?", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.
- account-research"Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question."
- analyzeAnswer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.
- architectureCreate or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
- audit-supportSupport SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.
- brand-reviewReview content against your brand voice, style guide, and messaging pillars, flagging deviations by severity with specific before/after fixes. Use when checking a draft before it ships, when auditing copy for voice consistency and terminology, or when screening for unsubstantiated claims, missing disclaimers, and other legal flags.
- brand-voice-enforcement>
- briefGenerate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.
- build-dashboardBuild an interactive HTML dashboard with charts, filters, and tables. Use when creating an executive overview with KPI cards, turning query results into a shareable self-contained report, building a team monitoring snapshot, or needing multiple charts with filters in one browser-openable file.
- build-zoom-botBuild a Zoom meeting bot, recorder, or real-time media workflow. Use when joining meetings programmatically, processing live media or transcripts, or combining Meeting SDK, RTMS, and backend services.