PROJECT MANAGEMENT
Require approval before mid-sprint scope is accepted
When an issue is added to an in-progress sprint in GitHub Projects, it posts an approval request to the scrum lead in Slack and only keeps the issue in the sprint if approved.
How it runs
The automated pipeline, trigger to output.
- TriggerIssue added to in-progress GitHub sprint iterationGitHub
- LogicConfirm iteration already started
- ActionSend approve/reject prompt to scrum lead in SlackSlack
- LogicBranch on approval decision
- OutputKeep and tag, or return issue to backlog in GitHubGitHub
What it does
This turns mid-sprint additions into a deliberate decision. Whenever an issue is moved into a sprint that is already underway, the workflow pauses and asks the scrum lead to approve or reject the addition in Slack. Approved issues stay and are tagged as accepted scope changes; rejected issues are automatically returned to the backlog so the committed sprint stays clean.
When to use it
Use it when your problem isn't visibility but discipline — work keeps getting jammed into active sprints without anyone signing off. The approval gate forces an explicit yes or no.
How it works
- 1A GitHub webhook fires when an issue is added to a sprint iteration already in progress.
- 2The flow confirms the iteration's start date has passed; if not, it exits silently.
- 3It sends an interactive approval prompt to the scrum lead in Slack with the issue title, points, and requester.
- 4On approval, it labels the issue as an accepted mid-sprint change in GitHub.
- 5On rejection, it removes the issue from the iteration and returns it to the backlog.
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.