PROJECT MANAGEMENT
Daily scope-change brief from Linear to Notion for the lead
Each morning, scans the active Linear cycle for issues added since planning, then assembles a one-page scope-change brief in Notion summarizing what crept in, its point cost.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily weekday-morning schedule
- ActionPull active cycle and post-start additions from LinearLinear
- LogicGroup additions by assignee, sum estimate vs remaining capacity
- ActionDraft accept/defer/split recommendation per item with an LLMOpenAI
- OutputWrite dated scope-change brief to Notion sprint databaseNotion
What it does
Produces a daily, decision-ready brief of everything that has entered the current sprint since it was committed. It groups the additions, totals their estimate against remaining capacity, and writes a structured Notion page the lead can review in two minutes before standup.
When to use it
Use it when scope changes are frequent enough that real-time pings become noise, but the lead still needs an accountable paper trail. The daily cadence batches creep into one reviewable artifact tied to the sprint.
How it works
- 1**Trigger** — A daily schedule fires each weekday morning.
- 2**Action** — Pull the active cycle and all issues added after its start date from Linear.
- 3**Logic** — Group additions by assignee and sum their estimates against the cycle's remaining capacity.
- 4**Action** — Use an LLM to draft a per-item accept / defer / split recommendation with a short rationale.
- 5**Output** — Create or update a dated scope-change brief page in the team's Notion sprint database.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect OpenAIModels, embeddings, files.
- 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.