Skip to content

Commit ededc4e

Browse files
leonardocouyleonardocouy
committed
feat: add daily-meeting-update skill for standup generation
Interactive daily standup/meeting update generator that conducts an interview (yesterday, today, blockers, discussion topics) and optionally pulls activity from GitHub/git/Jira if available.
1 parent 782cead commit ededc4e

4 files changed

Lines changed: 554 additions & 0 deletions

File tree

‎.claude-plugin/marketplace.json‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -531,6 +531,23 @@
531531
"sbi"
532532
]
533533
},
534+
{
535+
"name": "daily-meeting-update",
536+
"description": "Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', or wants to prepare for daily meeting. Conducts interview (yesterday, today, blockers, discussion topics) and optionally pulls activity from GitHub/git/Jira if available and approved by user.",
537+
"source": "./",
538+
"strict": false,
539+
"skills": [
540+
"./skills/daily-meeting-update"
541+
],
542+
"category": "professional",
543+
"keywords": [
544+
"professional",
545+
"standup",
546+
"daily",
547+
"meeting",
548+
"scrum"
549+
]
550+
},
534551
{
535552
"name": "professional-communication",
536553
"description": "Guide technical communication for software developers. Covers email structure, team messaging etiquette, meeting agendas, and adapting messages for technical vs non-technical audiences.",

‎README.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -126,6 +126,7 @@ Add skills to project knowledge or paste SKILL.md contents into the conversation
126126
| 🎯 Planning | [gepetto](skills/gepetto/README.md) | Detailed implementation planning |
127127
| 🎯 Planning | [requirements-clarity](skills/requirements-clarity/README.md) | Clarify requirements before coding |
128128
| 🎯 Planning | [ship-learn-next](skills/ship-learn-next/README.md) | Turn learning into actionable reps |
129+
| 👔 Professional | [daily-meeting-update](skills/daily-meeting-update/README.md) | Interactive daily standup generator |
129130
| 👔 Professional | [difficult-workplace-conversations](skills/difficult-workplace-conversations/README.md) | Navigate difficult conversations |
130131
| 👔 Professional | [feedback-mastery](skills/feedback-mastery/README.md) | Deliver constructive feedback |
131132
| 👔 Professional | [professional-communication](skills/professional-communication/README.md) | Technical communication guide |

‎skills/daily-meeting-update/README.md‎

Lines changed: 211 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,211 @@
1+
# Daily Meeting Update
2+
3+
Generate polished daily standup updates through an interactive interview process, optionally enriched with data from GitHub, Git, and Jira integrations.
4+
5+
## Purpose
6+
7+
The Daily Meeting Update skill helps developers prepare for daily standups or scrum meetings by:
8+
9+
1. **Gathering context automatically** - Detects and optionally pulls recent activity from GitHub, Git, and Jira
10+
2. **Conducting a structured interview** - Asks the right questions to capture what matters
11+
3. **Generating a clean update** - Produces a well-formatted Markdown summary ready to share
12+
13+
This skill bridges the gap between raw activity data (commits, PRs, tickets) and the human context that makes standups valuable (blockers, priorities, discussion topics).
14+
15+
## When to Use
16+
17+
Trigger this skill when you:
18+
19+
- Say **"daily"**, **"standup"**, **"scrum update"**, or **"status update"**
20+
- Want to **prepare for a daily meeting**
21+
- Need to **summarize your recent work** for the team
22+
- Want to **generate a meeting update** with GitHub/Jira context
23+
24+
**Example triggers:**
25+
26+
```
27+
"Help me with my daily"
28+
"Prepare my standup update"
29+
"Generate a scrum update"
30+
"What's my status for today's meeting?"
31+
```
32+
33+
## How It Works
34+
35+
The skill operates in three phases:
36+
37+
### Phase 1: Detect and Offer Integrations
38+
39+
The skill silently checks for available integrations:
40+
41+
| Integration | Detection Method |
42+
|-------------|------------------|
43+
| GitHub CLI | `gh auth status` succeeds |
44+
| Git | Current directory is a git repository |
45+
| Jira CLI | `jira` command exists |
46+
| Atlassian MCP | `mcp__atlassian__*` tools available |
47+
48+
If integrations are detected, you'll be asked whether to pull data and which repositories/projects to include. **Consent is always required** before accessing any data.
49+
50+
### Phase 2: Interview (with Insights)
51+
52+
The skill asks four key questions:
53+
54+
1. **Yesterday** - What did you work on since the last standup?
55+
2. **Today** - What will you work on today?
56+
3. **Blockers** - Any impediments or blockers?
57+
4. **Topics for Discussion** - Anything to bring up at the end of the meeting?
58+
59+
If data was pulled in Phase 1, it's shown as context during the interview to help trigger your memory ("I see you merged PR #123, anything else?").
60+
61+
### Phase 3: Generate Update
62+
63+
All information is combined into a clean Markdown update, including:
64+
65+
- Yesterday's accomplishments
66+
- Today's planned work
67+
- Blockers (if any)
68+
- PRs and reviews (if pulled from GitHub)
69+
- Jira tickets (if pulled)
70+
- Topics for discussion
71+
- Relevant links
72+
73+
## Key Features
74+
75+
- **Interview-first approach** - Tools supplement human context, they don't replace it
76+
- **Smart context awareness** - Shows pulled data during questions to trigger memory
77+
- **Consent-based data access** - Always asks before pulling from any integration
78+
- **Multi-repo support** - Can pull activity from multiple repositories
79+
- **Clean output** - Generates concise, readable Markdown ready for sharing
80+
- **Discussion topics** - Captures the valuable non-technical items that tools can't detect
81+
82+
## Usage Examples
83+
84+
### Basic Usage (No Integrations)
85+
86+
```
87+
User: "Help me prepare my daily"
88+
89+
Claude: "What did you work on yesterday?"
90+
User: "Fixed the authentication bug and reviewed a PR"
91+
92+
Claude: "What will you work on today?"
93+
User: "Continue the payment integration"
94+
95+
Claude: "Any blockers?"
96+
User: "Waiting on API credentials from the backend team"
97+
98+
Claude: "Any topic for the end of the daily?"
99+
User: "No"
100+
101+
[Claude generates update]
102+
```
103+
104+
### With GitHub Integration
105+
106+
```
107+
User: "Daily standup"
108+
109+
Claude: "I detected GitHub configured. Want me to pull your recent activity?"
110+
User: "Yes"
111+
112+
Claude: "Which repos should I check?"
113+
User: "my-app and api-service"
114+
115+
Claude: "Here's what I found:
116+
- Merged PR #120: fix login timeout
117+
- Opened PR #125: feat: add OAuth flow
118+
- 5 commits in my-app
119+
120+
Anything else you worked on yesterday?"
121+
User: "Also did research on payment providers"
122+
123+
[Interview continues...]
124+
```
125+
126+
### With Jira Integration
127+
128+
```
129+
Claude: "I see you have these tickets assigned:
130+
- PROJ-123: Implement OAuth flow (In Progress)
131+
- PROJ-456: Fix payment bug (To Do)
132+
133+
Will you work on any of these today?"
134+
User: "Yes, continuing PROJ-123 and starting PROJ-456"
135+
```
136+
137+
## Prerequisites
138+
139+
**Required:**
140+
- None - the skill works with manual input alone
141+
142+
**Optional (for enhanced functionality):**
143+
- **GitHub CLI** (`gh`) - For pulling commits, PRs, and reviews
144+
- **Git** - For local commit history
145+
- **Jira CLI** or **Atlassian MCP** - For pulling ticket information
146+
147+
## Output
148+
149+
The skill generates a Markdown document like this:
150+
151+
```markdown
152+
# Daily Update - 2026-01-22
153+
154+
## Yesterday
155+
- Worked on authentication feature
156+
- Research on payment providers
157+
- Merged PR #120 (fix: login timeout)
158+
- Opened PR #125 (feat: add OAuth flow)
159+
160+
## Today
161+
- Continue OAuth feature
162+
- Deploy to staging
163+
164+
## Blockers
165+
- No blockers
166+
167+
## PRs & Reviews
168+
- **Opened:** PR #125 - feat: add OAuth flow
169+
- **Merged:** PR #120 - fix: login timeout
170+
- **Reviews:** PR #123 (approved), PR #456 (changes requested)
171+
172+
## Topics for Discussion
173+
- Architecture of the new payments module
174+
175+
---
176+
*Links:*
177+
- https://github.com/org/repo/pull/125
178+
- https://github.com/org/repo/pull/120
179+
```
180+
181+
## Best Practices
182+
183+
### Do
184+
185+
- **Be specific in your answers** - "Fixed auth bug" is less useful than "Fixed session timeout causing users to lose work"
186+
- **Mention cross-team dependencies** - These often become discussion topics
187+
- **Include non-coding work** - Research, documentation, and planning count too
188+
- **Use discussion topics** - This is often the most valuable part of standup
189+
190+
### Avoid
191+
192+
- **Skipping the interview** - Even with tool data, your context is essential
193+
- **Overly long updates** - Keep to 15 bullets or less; standups should be under 2 minutes to read
194+
- **Raw ticket/PR numbers** - Always include titles or summaries for context
195+
- **Assuming one repo** - If you work on multiple projects, specify which ones to pull from
196+
197+
## Privacy and Security
198+
199+
- **Consent required** - The skill never pulls data without explicit approval
200+
- **Repository boundaries** - Only pulls from repos you explicitly approve
201+
- **No assumptions** - Never assumes tools are configured or authenticated
202+
- **Selective sharing** - You control what goes into the final update
203+
204+
## Related Information
205+
206+
| Item | Description |
207+
|------|-------------|
208+
| Trigger phrases | "daily", "standup", "scrum update", "status update" |
209+
| Interview questions | Yesterday, Today, Blockers, Discussion Topics |
210+
| Supported integrations | GitHub CLI, Git, Jira CLI, Atlassian MCP |
211+
| Output format | Markdown |

0 commit comments

Comments
 (0)