Menu
Prepare a standup document summarizing recent work activity across Git, GitHub, and Jira.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Set up or bootstrap a project with the claude-code-config tooling — setup-project.sh, install-tooling.sh, the layered hooks setup, and the new-repo runbook. Use when installing this config into a repo, running the setup scripts, vendoring the make-check tooling, or bootstrapping a new project.
Create a new "Later" backlog item (Learn / Research / Do / Read) from a configurable template.
Install or update the shared MkDocs Material style layer (Ink & Indigo on warm paper) in the current project.
Prepare technical analysis for backlog refinement meetings.
Capture a quick status update and append it to today's daily log.
Prepare end-of-week review notes summarizing the full week's work activity across all sources (Git, GitHub, Jira).
| name | standup |
| description | Prepare a standup document summarizing recent work activity across Git, GitHub, and Jira. |
| argument-hint | [<period>] [--output <path>] [--team] [--skip-jira|--skip-calendar] |
Prepare a standup document summarizing my recent work activity.
First, read GATHERING.md in this skill's directory — it defines the shared data-gathering steps (identity, git, GitHub PRs, Jira, calendar, error handling, delivery). This file defines only what is standup-specific.
$ARGUMENTS
/standup 48 hours, /standup since Monday, /standup 3 days--output <path> (default: ./standups/YYYY-MM-DD-standup.md)--team - Include team activity overview (opt-in)--skip-jira, --skip-calendarCompute $START_DATE / $END_DATE from the period and use them in all gathering steps.
Before the shared gathering steps, check for today's daily log at ./standups/YYYY-MM-DD-log.md.
If it exists, extract:
## Status Updates section): the user's own words about their work. Treat as high-priority context — prefer the user's phrasing when summarizing completed work and blockers.## Session Summaries section): auto-logged git commits from session-end hooks. De-duplicate against git log output by commit hash.Entries mentioning "blocked", "waiting", or "stuck" should surface as blockers. If the file does not exist, proceed normally.
--team)If --team is provided AND Jira MCP is available, query team activity (excluding the current user):
JQL: project = BIL AND updated >= '-24h' AND assignee != '<accountId>' ORDER BY assignee, updated DESC
Group results by assignee; summarize each member's tickets moved, key status changes, and blockers flagged — one line per team member.
# Standup - [DATE]
## Yesterday / Since Last Standup
- [Completed items with ticket refs, e.g., "Implemented auth flow (BIL-123)"]
- [Documentation updates]
- [Meetings attended]
## Today
- [Planned work from In Progress tickets]
- [Scheduled meetings/discussions]
- [Goals for the day]
## Blockers / Discussion Points
- [Any blockers flagged in Jira]
- [Items needing team input or decisions]
- [Dependencies on others]
---
### Activity Details
**Git Commits**: N commits across M files
- [Repo 1]: X commits - [summary of changes]
**Pull Requests**:
- [#123 - Title - Status (merged/open/draft)]
**Jira Tickets**:
| Ticket | Title | Status | Points |
|--------|-------|--------|--------|
| BIL-123 | Implement feature X | In Review | 3 |
**Calendar/Meetings** (if available):
- [Meeting name] - [outcome or action items]
---
### Team Activity (if --team flag used)
| Team Member | Recent Activity |
| ----------- | ---------------------------------- |
| [Name 1] | BIL-XXX: [brief], BIL-YYY: [brief] |
./standups/ (create the directory with mkdir -p ./standups if needed)