PROJECT MANAGEMENT
Flag Linear issues added after sprint commit and log them to a scope-creep ledger
Watches a Linear cycle for issues added after the sprint has started, then records each one in a Notion scope-creep ledger with the added point value and the person who requested…
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue added to active cycleLinear
- LogicAdded after cycle start date?
- ActionRead estimate, title, and requesterLinear
- LogicRoute unestimated issues to needs-sizing
- ActionAppend row to Notion scope-creep ledgerNotion
- OutputLedger row recorded for retro reviewNotion
What it does
When an issue is added to the active Linear cycle after its start date, this workflow captures it, reads the estimate and the requester, and appends a row to a Notion ledger so every mid-sprint addition is on the record with points attributed to a stakeholder.
When to use it
Run this when your team commits to a fixed scope at sprint planning but stakeholders keep dropping work into the cycle. It removes the end-of-sprint argument about "who added what" by logging additions as they happen.
How it works
- 1A Linear webhook fires whenever an issue is created or moved into the active cycle.
- 2A logic step compares the issue's added-to-cycle timestamp against the cycle start date and drops anything added before commit.
- 3An action reads the issue's estimate (points), title, and the requester field or last commenter to attribute the ask.
- 4A logic step skips issues with no estimate by routing them to a "needs sizing" tag instead of the ledger.
- 5An action appends a row to the Notion scope-creep ledger: issue, points, requesting stakeholder, date.
- 6The new ledger row is the durable output a lead reviews at retro.
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
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.
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.
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.
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…
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.