skill · from the engineering plugin
/standup
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.
- engineering plugin
- Slash command
you ›install the engineering plugin
metaphor ›Installed engineering. /standup is ready.
you ›/standup
metaphor ›Loaded the standup skill. What should I work on?
What the agent is told
This is the skill's SKILL.md, exactly what Metaphor reads before the task.
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.
Questions
What is the standup skill?
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.
How do I use standup in Metaphor?
Install the engineering plugin by asking the agent "install the engineering plugin", then type /standup in the composer.
What is a skill?
A skill is a set of written instructions the agent reads before it starts a kind of task. It changes how the agent works, not what it is allowed to do.
More from engineering
- /architectureSkillCreate or evaluate an architecture decision record (ADR).in engineering
- /code-reviewSkillReview code changes for security, performance, and correctness.in engineering
- /debugSkillStructured debugging session — reproduce, isolate, diagnose, and fix.in engineering
- /deploy-checklistSkillPre-deployment verification checklist.in engineering
- /documentationSkillWrite and maintain technical documentation.in engineering
- /incident-responseSkillRun an incident response workflow — triage, communicate, and write postmortem.in engineering