PROJECT MANAGEMENT
Require lead approval before mid-sprint Jira stories count
When a story is added to an active GitHub-linked sprint board, posts an approval request to the lead in Slack with accept/defer buttons and, on the lead's decision.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub issue added to active sprint project boardGitHub
- LogicConfirm sprint is in progress (not planning window)
- ActionSend lead an interactive Slack accept/defer requestSlack
- LogicBranch on the lead's button choice
- OutputLabel GitHub issue accepted-scope or deferred and confirmGitHub
What it does
Puts a human gate in front of scope creep. The moment a new issue lands in the running sprint, the lead gets an interactive Slack approval request; their click either tags the issue as accepted scope or moves it out and labels it deferred, so nothing silently bloats the commitment.
When to use it
Choose this when your team's rule is "additions need the lead's sign-off." It enforces that rule mechanically instead of relying on people to remember, and it leaves an auditable record of every mid-sprint decision.
How it works
- 1**Trigger** — GitHub fires when an issue is added to the active sprint project board.
- 2**Logic** — Confirm the sprint is already in progress; ignore items added during planning.
- 3**Action** — Send the lead an interactive Slack message with the issue summary and accept / defer buttons.
- 4**Logic** — Branch on the lead's choice.
- 5**Output** — Apply an "accepted-scope" or "deferred" label back on the GitHub issue and confirm in the thread.
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.