PROJECT MANAGEMENT
Scope-creep approval gate: agent investigates and proposes a re-baseline
On demand for a given Linear epic, an agent gathers the added issues since kickoff, drafts a re-baseline proposal with a revised target date.
How it runs
The automated pipeline, trigger to output.
- TriggerManual run with a target epic ID
- ActionFetch current issues and baseline from LinearLinear
- LogicDiff added issues and estimate schedule impact
- ActionSend re-baseline proposal to lead with approve/reject in SlackSlack
- LogicBranch on the lead's decision
- OutputApply new target date and note to the Linear epicLinear
What it does
Turns a scope-creep flag into an actionable decision. For a specified epic, an agent diffs the current child issues against the kickoff baseline, identifies which issues were added after kickoff, estimates schedule impact, and drafts a re-baseline proposal with a suggested new target date. It sends that to the lead in Slack as an interactive approval. On approval, it writes the new target date and a re-baseline note back to the Linear epic.
When to use it
Use it when a creep alert has fired and you want a structured, auditable re-baseline rather than an ad hoc Slack thread. Best for epics where the target date is a real external commitment.
How it works
- 1A manual trigger supplies the epic ID.
- 2The agent fetches current issues and the kickoff baseline from Linear.
- 3It isolates issues added after kickoff and reasons about schedule impact.
- 4A re-baseline proposal with a revised target date is drafted.
- 5Slack sends the proposal to the lead with approve and reject actions.
- 6On approval, Linear is updated with the new target date and a re-baseline comment.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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.