PROJECT MANAGEMENT
Catch PRs Doing Work Not in the Sprint
When a pull request opens during a sprint, checks whether its linked Linear issue belongs to the active cycle.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub pull request openedGitHub
- ActionParse branch and body for Linear issue key
- ActionVerify issue belongs to active cycleLinear
- LogicRoute clean vs no-issue vs out-of-sprint
- ActionComment on PR requesting a sprint issue linkGitHub
- OutputNotify lead of untracked workSlack
What it does
Intercepts opened pull requests and inspects the branch name and PR body for a Linear issue key. It then verifies that issue is part of the active cycle. PRs with no linked issue, or linked to work outside the current sprint, are flagged as untracked scope and commented on directly.
When to use it
Use this when engineers sometimes ship work that was never planned into the sprint, so the burndown looks fine while real effort leaks into off-plan tasks. It enforces the rule that in-sprint code maps to in-sprint issues.
How it works
- 1A GitHub webhook fires when a pull request is opened.
- 2The workflow parses the branch name and PR description for a Linear issue identifier.
- 3It queries Linear to confirm the issue exists and is assigned to the active cycle.
- 4A branch routes the PR into clean, no-issue, or out-of-sprint outcomes.
- 5For the two problem cases the workflow posts a GitHub comment asking for a linked sprint issue and notifies the lead in Slack.
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.