PROJECT MANAGEMENT
Weekly Sprint Velocity Roll-up from GitHub to Confluence
At sprint end, tallies merged pull requests and closed issues from GitHub, computes throughput stats, and publishes a velocity report page in Confluence for stakeholders.
How it runs
The automated pipeline, trigger to output.
- TriggerFriday sprint-close schedule
- ActionFetch merged PRs and closed issuesGitHub
- LogicAggregate throughput and cycle-time stats
- ActionWrite velocity narrativeOpenAI
- OutputPublish report page to ConfluenceConfluence
What it does
Generates the weekly engineering velocity report automatically. At the close of each sprint it gathers merged PRs and closed issues from your GitHub repos, computes throughput and cycle-time figures, has an LLM write the narrative summary, and publishes a clean Confluence page so leadership gets a consistent record without an engineer assembling slides.
When to use it
Use it when you report sprint outcomes to non-engineering stakeholders in Confluence and want the numbers and narrative produced consistently each week. Good for eng managers who currently hand-build status pages.
How it works
- 1A schedule fires every Friday afternoon at sprint close.
- 2The flow queries GitHub for PRs merged and issues closed during the sprint window across the configured repos.
- 3A logic step aggregates the raw events into counts, per-author throughput, and average time-to-merge.
- 4An LLM step turns the metrics into a readable velocity narrative with highlights and risks.
- 5The report publishes as a new Confluence page under the team's sprint space, ready to share.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Project Management workflows
Zoom Sprint-Retro Audio to Themed Linear Action Board
Transcribes a recorded Zoom sprint retrospective, clusters the discussion into themes, and creates assigned Linear issues for each action item with the spoken owner attached.
Escalate Overdue Cross-Team Dependencies to Owners and Stakeholders
Each morning checks Linear for dependency-labeled issues past their due date and nudges the owner in Slack, escalating to the requesting team's lead if it stays unresolved.
CEO-Authored Weekly Cross-Team Dependency Risk Briefing
Weekly, the CEO agent gathers all tracked dependencies across Linear and ClickUp, reasons about which handoffs threaten upcoming milestones.
Scan Notion Meeting Notes for Action Items and Open ClickUp Dependency Tasks
On a schedule, parses recently edited Notion meeting-notes pages for action items that one team owes another and creates a ClickUp task for each, with due date and owner mapped.
Sprint-Retro Recap to Slack with Owner DMs
After a Zoom retro, posts a themed recap to the team Slack channel and direct-messages each owner the specific action items they committed to during the call.
Turn GitHub Blocking Comments into Tracked Cross-Team Promises
When a reviewer comments that a PR is blocked waiting on another team, the flow registers a tracked dependency in Linear and notifies the team that owes the unblock.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.