PROJECT MANAGEMENT
Draft a sprint-retro scope-creep narrative from the ledger
At sprint end, an agent reads the Notion scope-creep ledger and Linear cycle data, then writes a plain-language retro narrative explaining what scope was added, by whom.
How it runs
The automated pipeline, trigger to output.
- TriggerEnd-of-cycle schedule
- ActionPull committed vs completed issues from LinearLinear
- ActionRead scope-creep ledger rows from NotionNotion
- LogicAgent correlates additions to stakeholders and impact
- ActionWrite retro narrative to Notion pageNotion
- OutputAnnounce retro narrative in SlackSlack
What it does
Converts a sprint's worth of raw ledger rows into a readable story for retrospective. The agent reasons over every post-commit addition, connects it to the originating stakeholder, weighs it against what got cut or slipped, and produces a narrative the team can discuss instead of a spreadsheet they ignore.
When to use it
Use it the day before sprint retro when you want an honest, sourced account of how scope evolved rather than gut feeling. Ideal for leads who want the conversation to start from facts.
How it works
- 1A schedule fires on the last day of the cycle.
- 2The agent pulls the cycle's committed vs completed issues from Linear and all matching rows from the Notion ledger.
- 3It correlates each addition to its stakeholder and quantifies added points against the original commitment.
- 4It drafts a narrative covering top scope drivers, recurring requesters, and likely impact on delivery.
- 5The narrative is written into a Notion retro page and announced in Slack as the output.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect NotionPages, databases, comments.
- 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
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.