Daily Meeting Update

Automate and integrate daily meeting updates to keep teams aligned and informed in real time

Category: productivity Source: softaworks/agent-toolkit

Daily Meeting Update is an AI skill that generates structured standup updates by analyzing recent development activity including commits, pull requests, and task completions. It covers activity summarization, blocker identification, progress reporting, and meeting note formatting that make daily standups efficient and informative.

What Is This?

Overview

Daily Meeting Update provides automated generation of standup-ready status updates from developer activity data. It addresses yesterday's work summarization by analyzing recent commits and merged pull requests, today's plan generation based on assigned tasks and pending reviews, blocker identification from stalled pull requests and failing CI builds, progress metrics showing sprint advancement and task completion rates, formatted output ready for standup meetings or async status channels, and team-level aggregation showing overall sprint health at a glance.

Who Should Use This

This skill serves developers preparing standup updates who want to save time, scrum masters compiling team progress for stakeholder reports, remote teams using async standup formats in Slack or Teams, and engineering managers tracking team velocity and blockers.

Why Use It?

Problems It Solves

Developers spend time before standup meetings trying to remember what they worked on yesterday. Updates are inconsistent in detail and format. Important blockers are mentioned but not tracked. Async standup updates in chat channels are tedious to write and often skipped.

Core Highlights

The skill pulls real activity data from Git and issue trackers rather than relying on memory. Standardized formatting makes updates easy to scan. Blocker detection highlights issues that may need team attention. Historical tracking shows progress patterns over time.

How to Use It?

Basic Usage

import subprocess
from datetime import datetime, timedelta

def generate_standup():
    yesterday = (datetime.now() - timedelta(days=1)).strftime("%Y-%m-%d")
    today = datetime.now().strftime("%Y-%m-%d")

    commits = subprocess.run(
        ["git", "log", f"--since={yesterday}", f"--until={today}",
         "--author=$(git config user.email)", "--oneline"],
        capture_output=True, text=True
    ).stdout.strip().split("\n")

    prs = subprocess.run(
        ["gh", "pr", "list", "--author=@me", "--state=open", "--json",
         "title,url,reviewDecision"],
        capture_output=True, text=True
    ).stdout

    update = f"## Standup Update - {today}\n\n"
    update += "### Done Yesterday\n"
    for commit in commits:
        if commit:
            update += f"- {commit}\n"
    update += "\n### Open PRs\n"
    update += format_prs(prs)
    return update

Real-World Examples

Standup Update - 2024-03-15

Done Yesterday:
- Implemented JWT refresh token rotation (PR #312)
- Fixed N+1 query in order listing endpoint
- Reviewed PR #308 (payment retry logic)

Today's Plan:
- Address review comments on PR #312
- Start work on rate limiting middleware (JIRA-456)
- Review PR #315 (user search endpoint)

Blockers:
- PR #312 needs security team review (requested 2 days ago)
- CI pipeline failing on integration tests (flaky DB connection)

Metrics:
- Sprint progress: 7/12 story points completed (58%)
- PRs in review: 2 (avg review wait: 1.5 days)

Advanced Tips

Integrate with your issue tracker API to automatically populate the "Today's Plan" section from assigned tickets. Set up a scheduled script that posts standup updates to Slack at a consistent time each morning. Track blocker age so recurring blockers are escalated automatically after a defined threshold.

When to Use It?

Use Cases

Use Daily Meeting Update when preparing for synchronous standup meetings, when posting async standup updates in team communication channels, when generating sprint progress reports for stakeholders, or when tracking development velocity over time.

Related Topics

Scrum methodology, Git activity analysis, project management integrations, team communication platforms, and sprint retrospective data all complement daily update generation.

Important Notes

Requirements

Git repository access for commit history analysis. GitHub or GitLab CLI for pull request status retrieval. Optionally, issue tracker API access for task and sprint data.

Usage Recommendations

Do: review generated updates before sharing to add context that automated analysis cannot capture. Include blockers prominently so they get addressed quickly. Use consistent formatting so team members can scan updates efficiently.

Don't: rely solely on automated updates without adding human context about priorities and challenges. Use standup updates as a productivity surveillance tool, as this undermines team trust. Skip mentioning blockers because they seem minor, since early visibility prevents delays.

Limitations

Automated updates capture activity but not effort, meaning complex debugging work that produced few commits may appear as low productivity. Work done outside version control like meetings and design work is not captured. The quality of generated updates depends on the quality of commit messages and issue tracking data.