PROJECT MANAGEMENT
Sprint capacity overcommit guard (Asana to Slack)
On a schedule, sums each assignee's estimated hours across active Asana projects and flags anyone whose load exceeds their sprint capacity in a Slack alert.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule: sprint planning cadence
- ActionFetch incomplete tasks + estimates across active Asana projectsAsana
- LogicAggregate hours per assignee vs. capacity
- LogicKeep only assignees over capacity
- OutputPost overcommit alert (or all-clear) to SlackSlack
What it does
It scans every active Asana project for the current sprint, totals the estimated hours assigned to each person, compares that against their per-sprint capacity, and posts a clear overcommit alert to Slack listing who is over and by how much.
When to use it
Run it at the start of every sprint, or nightly during planning, when work is spread across several Asana boards and no single view shows true per-person load. It catches silent overcommitment before it becomes missed commitments.
How it works
- 1A schedule fires at the planning cadence (e.g. each Monday 7am).
- 2Pull all incomplete tasks across active Asana projects, including assignee and the estimated-hours custom field.
- 3Aggregate hours per assignee and join against a capacity table (hours available this sprint).
- 4Branch: keep only assignees whose summed hours exceed their capacity.
- 5If anyone is over, format a ranked overcommit summary (name, assigned vs. capacity, delta).
- 6Post the alert to the planning Slack channel; if no one is over, post a short all-clear.
Set it up
What you configure once, before turning it on.
- 1Connect AsanaTasks, projects, milestones — everywhere.
- 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.