PROJECT MANAGEMENT
Log mid-sprint Linear tickets to a scope-creep ledger with stakeholder attribution
Watches a Linear sprint cycle and, whenever an issue is added after the cycle started, records it in a Notion scope-creep ledger along with who added it, the point estimate.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue added to active cycleLinear
- LogicKeep only issues added after cycle start date
- ActionFetch project + stakeholder-request label from LinearLinear
- ActionAppend attributed row to Notion scope-creep ledgerNotion
- OutputReturn new ledger row URLNotion
What it does
Keeps an auditable ledger of every ticket that lands in a sprint *after* the team committed to it. Each addition is captured with its estimate, the person who added it, and the stakeholder request it traces back to, so scope growth is never invisible at retro.
When to use it
Use it when your team commits to a sprint scope but tickets keep sneaking in mid-cycle and nobody can say later where they came from. Ideal for delivery leads who need defensible data on why a sprint slipped.
How it works
- 1A Linear webhook fires when an issue is added to the active cycle.
- 2A filter compares the issue's `addedToCycleAt` against the cycle start date; only issues added after commit pass.
- 3The flow reads the issue's parent project and any linked stakeholder request label to infer the originating requester.
- 4It appends a row to the Notion ledger database: title, estimate, added-by, requester, timestamp, and a link back to Linear.
- 5The new ledger row URL is the output, ready to surface in the sprint channel.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect NotionPages, databases, comments.
- 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.