Email Weekly Engineering Delivery Brief

What It Does

Fetches your GitHub repository activity every Monday morning, analyzes delivery health using structured metrics, and emails you a professional engineering brief with a GREEN/AMBER/RED health status, bottleneck diagnosis, contributor activity summary, and 3 specific actions to take this week — before your standup starts.

Why It Matters

Most engineering managers find out their team is blocked on Friday, not Monday. By then, a PR that sat unreviewed for 5 days has already slipped the sprint. Manual tracking means opening GitHub, counting PRs, checking ages, spotting who hasn't committed — 30 minutes of work before you can even think about what to do. This workflow does that analysis automatically every week and lands the insight in your inbox before your first meeting.

How It Works

1. Scheduled Trigger — Runs every Monday at 6:30 AM UTC (cron: 30 6 * * 1).
2. GitHub Node — Fetches all PRs from the last 7 days: open, merged, draft, and awaiting review.
3. AI Agent — Applies delivery health rules to assign GREEN/AMBER/RED status, calculates velocity metrics, identifies the top bottleneck with specific evidence, summarizes contributor activity, and generates 3 time-bound actions.
4. Gmail Node — Delivers a fully formatted HTML brief to your inbox.

What You Get

• Delivery health status (GREEN/AMBER/RED) with a one-sentence explanation of why
• Velocity metrics table: PRs opened, merged, awaiting review, average cycle time, commits, and stale issues
• Bottleneck of the Week with the specific PR, issue, or person named and one action to take today
• Contributor activity with burnout risk and bus-factor flags
• 3 concrete, time-bound actions for the week — not vague suggestions
• Professional HTML email formatted for readability, delivered before your Monday standup

Who It's For

• Engineering managers who run weekly delivery reviews and want the data pre-analyzed before the meeting
• Tech leads at startups where there is no dedicated project manager tracking PR health
• Staff engineers who informally own delivery health for their team and want a weekly pulse check
• CTOs at small companies who need a one-email view of whether engineering is flowing or blocked

Setup

1. Connect your GitHub account using a Personal Access Token (github.com/settings/tokens — scopes: repo, read:user).
2. Connect your Gmail account and grant all permissions with ongoing access.
3. Update the GitHub node to point to the repository you want to monitor.
4. Update the Gmail node with your recipient email address.

Customize It

• Change the repository: Edit the GitHub node settings to point to any repo you want to monitor.
• Change the delivery day: Edit the cron expression — e.g., 30 6 * * 5 for a Friday retrospective timing.
• Adjust health thresholds: Modify the GREEN/AMBER/RED thresholds in the AI agent prompt to match your team's normal velocity.

Timezone Note

The trigger runs at 6:30 AM UTC. Here are some common conversions:

Adjust the cron expression in the Scheduled Trigger node to match your preferred delivery time.