Weekly Engineering Velocity Report from GitHub and Linear
Every Monday, turn last week's merged PRs and closed Linear issues into a plain-English velocity read for the founding team.
This recipe reconstructs what engineering actually shipped last week — merged GitHub PRs, closed Linear issues, and cycle completion stats — dedupes the overlap, computes week-over-week velocity trends, and writes it up in decision-ready English a non-technical founder can read in ninety seconds. Every number traces to a real PR or issue, nothing is written to Notion or emailed until you approve, and the report is honest about slowing velocity and about what it cannot verify. The output is a staged package: a sourced velocity summary, a drafted founding-team email, and a matching Notion doc linked from that email.
How it runs
Multi-agent orchestration — here's the flow, step by step.
Resolve the reporting window, load recipients from memory, and run the consent/suppression gate on the recipient list before anything is drafted.
workflow orchestratorPull completed Linear issues and active-cycle stats for the window, each with its issue id/URL and cycle id.
pm scannerPull merged GitHub PRs and closed issues for the same window with PR number/URL and commit SHA.
web researcherNormalize both pulls and dedupe PR-that-closes-issue into single shipped-work items so nothing is double-counted.
data analystCompute and persist the stable run key and per-item dedupe keys before any drafting, establishing idempotency and resume-on-partial.
workflow orchestratorCompare the window against saved baselines to produce week-over-week and 4-week trend deltas per metric.
okr trackerTurn the trend into an honest velocity read (Accelerating/Steady/Slowing/Stalled) and surface bus-factor and carry-over risks.
business health scorerRender the supporting series into sourced metric tables and trend sparklines.
data analystWrite the plain-English velocity summary with numbers cited inline, legible to a non-technical founder.
executive briefing writerStructure the summary, highlights, metric tables, risk note, and shipped-item appendix into the full report body.
report formatterAssemble the Notion doc content in memory with every item deep-linked, staged but not yet created.
document writerDraft the founding-team email with the headline read and a placeholder for the Notion link, staged not sent.
email writerOn approval only, create the Notion doc and capture its real URL.
document writerOn approval only, inject the live doc URL into the email, send to the post-suppression recipients, optionally post a Slack summary, and mark the window delivered.
distributorRequired Agents
11- workflow-orchestrator
- pm-scanner
- web-researcher
- data-analyst
- okr-tracker
- business-health-scorer
- executive-briefing-writer
- report-formatter
- document-writer
- email-writer
- distributor
Connections
Required
Optional
What it does
- Windowed pull of merged PRs and closed issues from GitHub + cycle stats from Linear
- Dedupes PR-that-closes-issue so shipped work is never double-counted
- Week-over-week and 4-week velocity trends with an Accelerating/Steady/Slowing/Stalled read
- Bus-factor, carry-over, and unlinked-work risk flags
- Plain-English velocity summary legible without opening a single link
- Recipient consent/suppression gate before any send
- Idempotent per-window run key so re-runs never duplicate the email or doc
- Notion doc + founding-team email staged for one-click approval, nothing sent early
Example prompt
Every Monday send the founding team a plain-English summary of what engineering shipped last week from GitHub and Linear, with a link to a Notion doc.
Ready to deploy Weekly Engineering Velocity Report from GitHub and Linear?
Start free. One click, full agent orchestration.
Get Started Free →