PROJECT MANAGEMENT
Daily Sprint Points-Delta Report to Coda
Each morning compares the current Linear cycle's committed points against what it held at sprint start, then writes the delta and a creep percentage to a Coda tracking doc.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily weekday-morning schedule
- ActionSum committed points and unestimated count in active cycleLinear
- ActionRead or seed sprint baseline rowCoda
- LogicCompute points-added delta and creep percentage
- OutputAppend dated delta row to Coda trackerCoda
What it does
Once per day, the workflow snapshots the active Linear cycle's total estimated points and unestimated issue count, compares them to the baseline captured on the sprint's first day, and records the running delta in a Coda table. Over the sprint you get a clean trend of how scope grew.
When to use it
Use this when you want a quiet daily record of scope drift rather than real-time pings, and you already run sprint reporting in Coda. It turns "the sprint felt heavier than planned" into a number your team can review at retro.
How it works
- 1A daily schedule triggers each weekday morning.
- 2The workflow pulls all issues in the active cycle from Linear and sums committed points plus counts issues with no estimate.
- 3It reads the sprint's baseline row from the Coda tracking table; on day one it writes that baseline instead.
- 4Logic computes points added since baseline and a creep percentage.
- 5A new dated row is appended to the Coda doc with today's total, the delta, and the creep percent for the burn-up chart.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect CodaDocs, packs, automations.
- 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.