PROJECT MANAGEMENT
Agent reschedules downstream Asana milestones when a Linear blocker slips
When a Linear issue blocking other work slips its target date, an agent estimates the cascade, proposes new dates for the affected downstream Asana tasks.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear blocker issue date slipsLinear
- ActionWalk dependency chain to downstream Asana tasksAsana
- LogicAgent estimates cascade and proposed new dates
- LogicRoute large cascade for human approval
- OutputPost proposed re-plan to Slack for approvalSlack
What it does
When a Linear issue that blocks other work moves its target date, an agent reasons about the knock-on effect: it reads the blocked chain, estimates how far each downstream Asana task should shift, and drafts a concrete re-plan rather than just an alert. The proposal goes to Slack for a human to approve before anything changes.
When to use it
Use it when a slip on one upstream issue ripples through a dependency chain and someone normally has to manually recompute every downstream date. The agent does that reasoning and hands you a ready-to-approve plan.
How it works
- 1A Linear issue flagged as a blocker has its target/due date pushed.
- 2The agent walks the dependency chain to find downstream Asana tasks.
- 3It estimates a proposed new date for each, accounting for the slip size and existing slack.
- 4A logic gate routes large cascades (multiple milestones affected) for human approval versus auto-apply.
- 5The agent posts the proposed re-plan to Slack with per-task old/new dates for one-click approval.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect AsanaTasks, projects, milestones — everywhere.
- 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
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.