PROJECT MANAGEMENT
Linear Kickoff Baseline Snapshotter
When a Linear epic moves into an in-progress state, captures its acceptance criteria as an immutable baseline in Postgres and mirrors the locked scope to a Notion record…
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue state changed webhookLinear
- LogicFilter epics entering in-progress without baseline
- ActionParse acceptance-criteria block
- ActionStore immutable baseline in PostgresPostgres
- OutputCreate locked scope record in NotionNotion
What it does
This workflow establishes the source of truth that scope-creep detection depends on. The moment an epic transitions from planning into active work, it freezes the acceptance criteria exactly as agreed and stores them as a baseline. It then writes a read-only scope-of-record entry into Notion so everyone can see precisely what was committed to at kickoff, with a timestamp and the person who moved it.
When to use it
Run this as the companion to any drift detector. Use it on every epic your team commits to, so that later changes can be measured against an honest starting point instead of a moving target.
How it works
- 1A Linear webhook fires on an issue state change.
- 2A filter passes only epics entering the configured in-progress state that have no existing baseline.
- 3The acceptance-criteria block is parsed from the epic description.
- 4The baseline is written to Postgres keyed by epic ID with a kickoff timestamp.
- 5A locked scope-of-record page is created in Notion linking back to the Linear epic.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect NotionPages, databases, comments.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.