PROJECT MANAGEMENT
Draft a sprint-retro scope-creep narrative for the team
On sprint close, gathers the late-added tickets from Linear, has the CEO agent reason about why scope crept and which sources drove it.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled run at sprint close
- ActionPull post-commit cycle additions with metadataLinear
- ActionCEO agent analyzes creep drivers and themesOpenAI
- LogicDraft retro narrative with recommendations
- OutputPost retro narrative to team Slack channelSlack
What it does
Raw creep numbers don't tell you why scope grew. This agent-driven workflow collects the tickets that entered the Linear cycle after commit, then has the CEO agent analyze patterns — which requesters, which projects, which kinds of work — and write a short retro narrative explaining what happened and what to change next sprint. The narrative is delivered to the team for the retro discussion.
When to use it
Use it when you want more than a tally: a thoughtful, human-readable read on the drivers of scope creep and concrete suggestions, ready to drop into a retrospective.
How it works
- 1A scheduled trigger fires at sprint close.
- 2The flow pulls all post-commit additions to the active Linear cycle with their requesters, labels, and points.
- 3The CEO agent reasons over the set to identify the dominant creep sources and recurring themes.
- 4It drafts a concise retro narrative with findings and two to three recommendations.
- 5The narrative is posted to the team's Slack channel for the retrospective.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect OpenAIModels, embeddings, files.
- 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.
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…
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.
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.
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.