Project Management workflows

On a Linear epic edit, an AI agent compares the new acceptance criteria against the kickoff baseline to judge whether the change is true scope expansion versus a clarification.

Daily matches recently completed Linear and GitHub work against open cross-team dependency tasks in ClickUp, auto-closes the ones that are satisfied.

An agent watches new Loom standups, extracts blockers, decides whether each belongs to engineering, design, or ops, and opens it in the right board (ClickUp or Linear)…

Each week an agent traces dependency chains across Linear, ClickUp, and Asana, identifies the longest at-risk critical paths.

Transcribes each field voice note, stores the full transcript and metadata in Postgres for the record.

Every Friday, pulls the active Linear sprint's issue data, has an LLM write a plain-English health summary, publishes it as a Notion page.

At each sprint close, records the completed cycle's velocity and metrics to a Postgres table.

On each region's shift change, appends a timestamped, structured handoff entry to a single Notion handoff log page.

Each morning, gathers the prior day's merged PRs and commits from GitHub, ties them back to the Linear issues they reference.

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.

Every Monday, ranks all active Linear epics by percentage point growth since kickoff, publishes a portfolio scope-creep digest page in Confluence.

When a Linear issue is marked blocked near the end of a shift, immediately drafts a focused escalation note and sends it to the incoming region's on-call via Slack and Outlook…

An agent reviews the Zoom retro transcript against the team's open Linear backlog, drafts themed action items.

Watches a Monday board for columns that exceed their WIP limit, drafts a rebalance plan with an LLM, and DMs the column owner on Slack to confirm before any cards move.

Each morning summarizes which Monday columns are near or over their WIP limits, has an LLM explain the likely bottleneck, and posts a ranked digest to a Slack channel for standup.

Reads each new Loom standup transcript, detects clearly stated blockers, and creates a Linear issue for any blocker that isn't already tracked.

Tracks issues referenced across consecutive Loom standups and flags any that have been talked about repeatedly while showing zero Linear movement.

Tracks how long each detected circular dependency has gone unresolved and escalates up a ladder: a Slack nudge to owners first.

Every Friday it pulls completed vs. committed work across the sprint, has an agent write a plain-English velocity-drift narrative, publishes it to a Notion page.

Each week, an agent reads dependencies from Asana and GitHub, reasons about which tasks block the most downstream work.

Each morning, collects the team's Loom async-standup videos, reads their transcripts, and cross-checks who said they were blocked against which Linear issues actually moved.

When shifting a slipped dependency chain would push a downstream milestone past a hard deadline, this escalates by drafting the conflict.

On a weekly schedule, compares every linked Linear epic against its Monday roadmap item and posts a digest of mismatched dates, statuses, and orphaned items to Slack.

Mid-sprint, scans Linear for issues that are behind schedule or have stalled, ranks them by risk, and sends a prioritized at-risk digest to the team via email and Discord.

Weekly, the CEO agent gathers all tracked dependencies across Linear and ClickUp, reasons about which handoffs threaten upcoming milestones.

When a new blocking link is added in Monday or Linear, traverses the combined dependency graph to detect cycles and alerts the team in Slack before a deadlock is committed.

On a schedule, pull initiatives from Asana and engineering epics from Linear, reconcile them against a master RACI tracking sheet in Airtable.

A webhook triggers a point-in-time capacity scan across Asana boards, writes each assignee's load and overage to an Airtable log, and Slacks a summary of who is overcommitted.

When a Linear epic is marked done, it flips the linked Monday roadmap item to Done and appends a dated entry to a Notion shipped-roadmap changelog.

On request, an agent reviews every team's committed Linear load against PTO-adjusted capacity and BigQuery velocity history.

Parses a Zoom retro transcript, separates engineering blockers from general action items, opens GitHub issues for the blockers.

On a blocker slip in Asana, an agent walks the dependency chain across Asana and Monday, estimates the cascade delay, drafts revised target dates with rationale.

Watches blockers raised in Loom standups and, when the same blocker recurs across multiple days without the linked Linear issue closing, escalates it to the team lead via Slack…

On a schedule, finds blockers across boards that have stayed unresolved past a threshold while downstream tasks pile up behind them.

Builds a weekly digest of every at-risk dependency on a Monday board, logs each one to a Google Sheet for trend tracking, and emails a ranked summary of the top risks via Gmail.

Once a week, an agent aggregates blocked items from Asana, Linear, and a Coda tracker, reconciles duplicates across tools.

On each roadmap or issue change, captures the current cross-tool blocking graph into a Postgres table so you can query critical paths and bottleneck history over time.

Fifteen minutes before a recurring standup, an agent reviews cross-board dependencies in Linear and ClickUp and posts a short risk briefing to the team channel so the meeting…

An agent transcribes a field voice note, decides which of several project boards it belongs to, splits it into per-owner action items.

Transcribes a field worker's voice note with ElevenLabs, extracts action items with OpenAI.

On a weekly schedule, gathers every Loom design handoff recorded that week, matches each to its Linear ticket, and publishes a single Confluence page summarizing scope and status.

Takes commitments from a Zoom kickoff transcript, writes each as an item on a Monday board.

On a new Loom recording, creates a Notion handoff page that embeds the Loom, links the Figma file mentioned in the description.

Webhook-driven guard that records each capacity breach and, when a person stays over capacity past a grace window with no rebalance, escalates to the sprint lead in Teams…

At quarter close, reads every sprint's commitment-versus-delivered history from BigQuery, charts which teams chronically over-commit.

Daily check that compares each active Linear epic's current child-issue point total against the baseline captured at kickoff.

Monthly, queries the Postgres cycle-time history, has the CEO agent write a plain-English flow-efficiency review explaining what changed and why.

Watches a team's daily standup channel for sentences where someone promises to deliver something to another team.

On a Slack slash-command, an agent pulls the draft sprint from Linear, weighs it against velocity history.

When a squad member asks the CEO agent for a catch-up, it reads what changed in Linear and the recent handoff Slack thread since they last signed off and replies…

At the end of a squad's working window, gathers everything that moved in Linear that day and posts a structured handoff baton note to the next region's Slack channel…

When an issue is added to an in-progress Linear sprint, an LLM judges whether it is a true emergency or deferrable scope creep.

When a circular dependency is found in Linear, an agent reasons over the blocked issues to recommend which single link to cut to break the loop with least disruption.

On sprint close, gathers the late-added tickets from Linear, has the CEO agent reason about why scope crept and which sources drove it.

Every weekday morning, summarizes the last 24 hours of Linear issue activity into a written standup digest and posts it to your team's Slack channel.

Fires whenever an issue is added to the active Linear cycle mid-sprint, decides whether it counts as unplanned scope creep.

Reads the daily standup thread in Slack, uses AI to extract concrete action items, and files each as an assigned Linear issue with a reply-back link.

At shift end, finds pull requests still awaiting review or with unresolved comments and hands them to the incoming region with a per-PR baton note in Slack.

When a ticket is added to a locked sprint, an agent reads its description and the sprint's committed work, judges urgency, and either drafts a defer-to-next-cycle note…

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.