PROJECT MANAGEMENT
End-of-sprint scope-creep report from a Postgres snapshot to Confluence
At sprint close, snapshots the final Linear cycle into Postgres, diffs it against the stored committed baseline.
How it runs
The automated pipeline, trigger to output.
- TriggerSprint-end schedule
- ActionSnapshot closed Linear cycle to PostgresPostgres
- ActionRead committed baseline from PostgresPostgres
- LogicDiff baseline vs final, compute velocity impact
- OutputPublish retro report to ConfluenceConfluence
What it does
This workflow produces the definitive scope record for a sprint retro. It captures the final state of the cycle, compares it to the baseline locked at planning, and writes a clean, shareable Confluence page so the retro starts from facts rather than memory.
When to use it
Use it at the end of each sprint when you run retros and need an auditable account of what was committed, what was added after lock, and how velocity was affected. Best for teams that document sprint outcomes in Confluence.
How it works
- 1A schedule trigger fires at the configured sprint-end time.
- 2The workflow pulls the closed cycle's final issues from Linear and writes a snapshot row to Postgres.
- 3It reads the committed baseline snapshot stored in Postgres from planning day.
- 4A diff step itemizes post-lock additions, drops, and re-estimates, computes committed-vs-delivered velocity, and attributes each addition to its requester.
- 5A Confluence retro page is created with the itemized table and velocity summary.
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.