PROJECT MANAGEMENT
Snapshot Sprint Velocity to Postgres and Chart the Trend
At each sprint close, records the completed cycle's velocity and metrics to a Postgres table.
How it runs
The automated pipeline, trigger to output.
- TriggerSprint-close schedule fires
- ActionFetch completed cycle issues from LinearLinear
- LogicRoll up planned, completed, carryover points
- ActionInsert velocity snapshot into PostgresPostgres
- ActionSummarize trailing trend with LLMOpenAI
- OutputPost velocity and trend to SlackSlack
What it does
Builds a durable velocity history instead of letting each sprint's numbers vanish. On sprint completion it writes the cycle's planned points, completed points, and carryover to Postgres, then reads the last several snapshots to describe the throughput trend.
When to use it
When you want evidence-based capacity planning rather than guessing how much the team can take on. Run it the day a cycle ends. Best for teams that estimate in points and want a queryable record for retros and forecasting.
How it works
- 1A schedule fires when the cycle ends.
- 2Pull the just-completed cycle's issues and estimates from Linear.
- 3Roll up planned points, completed points, and carryover into one snapshot row.
- 4Insert the snapshot into the velocity history table in Postgres.
- 5Read the trailing snapshots and have an LLM summarize the trend direction.
- 6Post the velocity number and trend note to the team Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.