PROJECT MANAGEMENT
Attribute GitHub PRs opened against a milestone after it was frozen
When a pull request is added to a GitHub milestone after that milestone's planned freeze date, this workflow records the PR, its size, and the author or linked requester…
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub PR assigned to milestoneGitHub
- LogicAssigned after milestone freeze date?
- ActionRead diff size and resolve requesterGitHub
- LogicBucket PR size into S/M/L
- ActionAppend PR to Airtable scope ledgerAirtable
- OutputAlert engineering lead in SlackSlack
What it does
For teams that plan by GitHub milestones, this catches PRs slotted into a milestone after the freeze date, estimates their size from the diff, attributes them to the author or the requester named in the linked issue, and logs them while alerting the lead.
When to use it
Use it when your delivery boundary is a GitHub milestone rather than a Linear cycle, and out-of-plan PRs keep appearing late. It gives engineering managers a defensible record of unplanned work and who asked for it.
How it works
- 1A GitHub webhook fires when a PR is assigned to a milestone.
- 2A logic step compares the assignment time to the milestone's stored freeze date and ignores PRs added before it.
- 3An action pulls the PR's changed-lines count as a size proxy and resolves the requester from the linked issue or PR author.
- 4A logic step classifies size into S/M/L buckets for the ledger.
- 5An action appends the PR, size bucket, and attributed stakeholder to an Airtable scope ledger.
- 6An output posts a short alert to the engineering lead's Slack so the addition is acknowledged in real time.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect AirtableBases, tables, views, automations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.
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.
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.
Log every dependency slip to a Notion register and email the affected leads
On any Asana dependency slip, appends a structured row to a Notion blocker register and emails the leads of the downstream teams so there is both an auditable record and a direct…
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.