PROJECT MANAGEMENT
End-of-Sprint Scope-Creep Retro Summary
At sprint close, gathers every issue added to the cycle after it started, summarizes who added what and the total unplanned points.
How it runs
The automated pipeline, trigger to output.
- TriggerSprint end-date schedule
- ActionFetch issues added after cycle startLinear
- LogicAggregate unplanned points and group by requester
- ActionAgent writes creep narrative and one suggestion
- OutputPublish dated Confluence retro pageConfluence
What it does
When a Linear cycle ends, the workflow collects all issues that entered the cycle after its start date, totals the unplanned points, groups additions by requester, and produces a written summary of how and where scope crept. The result is published as a Confluence page ready to drop into the retro.
When to use it
Use this when retros keep glossing over scope creep because nobody assembled the evidence. It hands the team a factual record of mid-sprint additions instead of relying on memory.
How it works
- 1A schedule fires on the sprint's end date.
- 2The workflow queries Linear for the just-ended cycle and filters to issues added after the start date.
- 3It aggregates unplanned points and groups additions by who requested them.
- 4An agent writes a concise narrative summarizing the magnitude and likely sources of creep with one improvement suggestion.
- 5The summary plus a per-requester table is published as a dated Confluence retro page.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 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.