PROJECT MANAGEMENT
Catch GitHub PRs that reference tickets not in the committed sprint
On every opened pull request, extracts the referenced Linear ticket and checks it against the locked sprint scope; if the PR is delivering uncommitted work, it comments on the PR…
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub pull request openedGitHub
- LogicExtract Linear ticket reference from PR
- ActionLook up ticket and committed-scope membership in LinearLinear
- LogicBranch: committed vs uncommitted work
- ActionComment on the GitHub PRGitHub
- OutputPing PR author in Slack to confirm or deferSlack
What it does
This workflow catches scope creep at the point of code, not just the board. When a PR is opened against work that was never in the committed sprint, it flags the mismatch right on the PR so the team decides consciously whether to absorb it.
When to use it
Use it when engineers sometimes pick up unplanned work and ship it without it ever appearing as committed scope. Ideal for teams enforcing that in-sprint code maps to committed tickets.
How it works
- 1A GitHub webhook fires when a pull request is opened.
- 2The workflow parses the PR title and body for a Linear ticket reference.
- 3It looks up that ticket in Linear and checks whether it belongs to the current cycle's committed scope set.
- 4A branch decides: committed work passes silently; missing or post-lock tickets are flagged.
- 5For flagged PRs it posts a comment on the GitHub PR and sends the author a Slack message asking them to confirm the addition or defer it.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 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.