PROJECT MANAGEMENT
Guard a locked GitHub milestone and request PM approval for late issues
Triggers when an issue is added to a GitHub milestone past its lock label, estimates effort from issue size labels.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub issue added to a milestoneGitHub
- LogicCheck milestone is scope-locked and issue is new
- ActionMap issue size label to effort estimateGitHub
- OutputOpen PM approval thread in SlackSlack
- ActionRemove from milestone and comment on rejectionGitHub
What it does
Protects a frozen GitHub milestone from late additions. The moment an issue lands in a milestone that carries a `scope-locked` marker, the workflow tallies the added effort from size labels and routes a sign-off request to the PM, auto-removing the issue from the milestone if it is rejected.
When to use it
Ideal for engineering teams that plan releases as GitHub milestones and treat the milestone scope as fixed once development starts. Use it to stop unplanned issues from quietly inflating a release.
How it works
- 1A GitHub webhook fires on the `milestoned` issue event.
- 2A logic step confirms the milestone carries the `scope-locked` label and the issue is new to it.
- 3An action reads the issue's size label (S/M/L/XL) and maps it to estimated days.
- 4A Slack message opens an approval thread tagging the milestone owner with the effort estimate.
- 5On rejection, an action removes the issue from the milestone and comments the decision back on GitHub.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.