Daily Meeting Update

# Daily Meeting Update

Generate polished daily standup updates through an interactive interview process, optionally enriched with data from GitHub, Git, and Jira integrations.

## Purpose

The Daily Meeting Update skill helps developers prepare for daily standups or scrum meetings by:

1. **Gathering context automatically** - Detects and optionally pulls recent activity from GitHub, Git, and Jira
2. **Conducting a structured interview** - Asks the right questions to capture what matters
3. **Generating a clean update** - Produces a well-formatted Markdown summary ready to share

This skill bridges the gap between raw activity data (commits, PRs, tickets) and the human context that makes standups valuable (blockers, priorities, discussion topics).

## When to Use

Trigger this skill when you:

- Say **"daily"**, **"standup"**, **"scrum update"**, or **"status update"**
- Want to **prepare for a daily meeting**
- Need to **summarize your recent work** for the team
- Want to **generate a meeting update** with GitHub/Jira context

**Example triggers:**

```
"Help me with my daily"
"Prepare my standup update"
"Generate a scrum update"
"What's my status for today's meeting?"
```

## How It Works

The skill operates in three phases:

### Phase 1: Detect and Offer Integrations

The skill silently checks for available integrations:

| Integration | Detection Method |
|-------------|------------------|
| Claude Code History | `~/.claude/projects` directory exists with `.jsonl` files |
| GitHub CLI | `gh auth status` succeeds |
| Git | Current directory is a git repository |
| Jira CLI | `jira` command exists |
| Atlassian MCP | `mcp__atlassian__*` tools available |

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.

### Phase 2: Interview (with Insights)

The skill asks four key questions:

1. **Yesterday** - What did you work on since the last standup?
2. **Today** - What will you work on today?
3. **Blockers** - Any impediments or blockers?
4. **Topics for Discussion** - Anything to bring up at the end of the meeting?

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?").

### Phase 3: Generate Update

All information is combined into a clean Markdown update, including:

- Yesterday's accomplishments
- Today's planned work
- Blockers (if any)
- PRs and reviews (if pulled from GitHub)
- Jira tickets (if pulled)
- Topics for discussion
- Relevant links

## Key Features

- **Interview-first approach** - Tools supplement human context, they don't replace it
- **Smart context awareness** - Shows pulled data during questions to trigger memory
- **Consent-based data access** - Always asks before pulling from any integration
- **Multi-repo support** - Can pull activity from multiple repositories
- **Clean output** - Generates concise, readable Markdown ready for sharing
- **Discussion topics** - Captures the valuable non-technical items that tools can't detect

## Usage Examples

### Basic Usage (No Integrations)

```
User: "Help me prepare my daily"

Claude: "What did you work on yesterday?"
User: "Fixed the authentication bug and reviewed a PR"

Claude: "What will you work on today?"
User: "Continue the payment integration"

Claude: "Any blockers?"
User: "Waiting on API credentials from the backend team"

Claude: "Any topic for the end of the daily?"
User: "No"

[Claude generates update]
```

### With GitHub Integration

```
User: "Daily standup"

Claude: "I detected GitHub configured. Want me to pull your recent activity?"
User: "Yes"

Claude: "Which repos should I check?"
User: "my-app and api-service"

Claude: "Here's what I found:
- Merged PR #120: fix login timeout
- Opened PR #125: feat: add OAuth flow
- 5 commits in my-app

Anything else you worked on yesterday?"
User: "Also did research on payment providers"

[Interview co