PROJECT MANAGEMENT
Capture epic kickoff baselines into a Notion scope ledger
When a Linear epic moves into its In Progress state, this snapshots its child-issue point total, scope, and target date as the official kickoff baseline and records it as a row…
How it runs
The automated pipeline, trigger to output.
- TriggerLinear epic enters In Progress stateLinear
- LogicConfirm it is an epic with no existing baseline
- ActionFetch child issues and point estimates from LinearLinear
- LogicCompute baseline points, count, and target date
- OutputWrite baseline row to Notion scope ledgerNotion
What it does
Watches Linear for epics transitioning into an active state and captures a one-time baseline: total child-issue points, issue count, and target date at the moment work starts. It writes that baseline as a row in a Notion database so every later scope-creep check has a trustworthy zero point to measure against.
When to use it
Use it as the companion to any scope-creep detector. Without a recorded kickoff baseline, growth can only be guessed at. Run this once per epic so future comparisons are exact rather than approximate.
How it works
- 1A Linear event fires when an epic enters its In Progress state.
- 2A filter confirms it is an epic and that no baseline row already exists for it.
- 3Linear is queried for the epic's full child-issue list and their point estimates.
- 4The workflow computes total points, issue count, and reads the target date.
- 5Notion receives a new row in the scope ledger with the epic ID, baseline points, count, target date, and timestamp.
- 6The created row link is returned for reference.
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.