PROJECT MANAGEMENT
Weekly scope-creep trend report for sprint retros
At the end of each week, tallies how many points were added to the active cycle after start versus the original commitment, compares it to prior weeks from a Postgres log.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly end-of-sprint schedule
- ActionDerive injected points from Linear cycle estimatesLinear
- ActionAppend week to Postgres history and read recent weeksPostgres
- LogicCompute trend and flag if over threshold
- OutputPublish trend report to Confluence retro spaceConfluence
What it does
Measures scope discipline over time. It computes this week's injected-points figure, appends it to a running history, and renders a trend showing whether mid-sprint additions are getting better or worse sprint over sprint — the evidence a retro needs to act on creep rather than just complain about it.
When to use it
Use it when you want creep treated as a tracked metric, not an anecdote. It gives team leads and EMs a longitudinal view to bring to retros and to defend or renegotiate planning capacity.
How it works
- 1**Trigger** — A weekly schedule fires at end of sprint week.
- 2**Action** — Pull the cycle's committed-at-start estimate and current total from Linear; derive injected points.
- 3**Action** — Append the week's figure to a scope-history table in Postgres and read back recent weeks.
- 4**Logic** — Compute the trend and flag if injected points exceeded a configured threshold.
- 5**Output** — Publish a formatted trend report page to the team's Confluence retro space.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 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.