PROJECT MANAGEMENT
Scope-Change Justification Gate for Linear Epics
When acceptance criteria are added to a locked Linear epic, requires a justification comment within a window; if none appears, reopens the scope question by re-labeling the epic…
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue updated webhookLinear
- LogicFilter locked epics with changed description
- ActionDiff baseline vs current criteriaPostgres
- LogicCheck comments for matching justificationLinear
- ActionApply needs-scope-review labelLinear
- OutputNotify lead in SlackSlack
What it does
This workflow enforces a lightweight governance rule: any scope added to a committed epic must be explained. When new acceptance criteria are detected, it checks whether a justification comment was left referencing the change. If the criteria grew but no rationale was recorded, it flags the epic with a needs-scope-review label and pings the lead, turning silent additions into an explicit decision.
When to use it
Use it on teams that allow mid-sprint scope changes but want every one of them to be deliberate and documented. It is ideal where unexplained requirement growth has historically wrecked commitments.
How it works
- 1A Linear webhook fires on an issue update.
- 2A filter passes locked epics whose description changed.
- 3The baseline from Postgres is diffed against current criteria to confirm real additions.
- 4A branch checks recent comments for a justification matching the added scope.
- 5If a justification exists, the workflow records it and exits quietly.
- 6If none exists, a needs-scope-review label is applied in Linear and the lead is notified in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.