daily-meeting-update_skill

Overview

This skill generates an interactive daily standup/meeting update by conducting a four-question interview and optionally pulling recent activity from GitHub, Jira, and Claude Code session history. It asks for consent before accessing any integrations and combines tool data with user answers to produce a concise, formatted Markdown update. The output is designed to be team-ready and under two minutes to read.

How this skill works

The skill silently detects available integrations, offers them to the user, and pulls approved data (commits, PRs, reviews, Jira tickets, Claude Code sessions) before the interview. It then conducts a focused interview covering Yesterday, Today, Blockers, and Topics for Discussion, using pulled data as context to prompt smarter follow-ups. Finally, it merges answers and tool insights into a clean Markdown daily update with links and summaries.

When to use it

• When preparing a daily standup or scrum update
• When asked for a status update or morning update
• Before or during a team sync to summarize recent work
• When you want to recall work from Claude Code sessions not recorded in Git/Jira
• When you need a quick, shareable Markdown summary for the team

Best practices

• Always consent to integrations before pulling data; the interview is primary, tools are supplementary
• Select only relevant Claude Code sessions and approved repos to avoid exposing personal work
• Summarize commit/PR/ticket items into readable outcomes rather than raw messages
• Answer the four interview questions with concrete outcomes and next steps to keep updates <2 minutes to read
• Include links for PRs and tickets but add short titles or summaries for context

Example use cases

• Morning standup: pull yesterday’s PRs and Claude Code sessions, answer the four questions, and produce a shareable Markdown update
• Pre-meeting prep: gather recent Jira ticket updates and commits, surface likely talking points, and highlight blockers
• On-call handoff: summarize what was fixed yesterday, what remains, and any outstanding issues for the next engineer
• Remote team sync: consolidate scattered activity (git, Jira, Claude Code) into a single clear update for async consumption