PROJECT MANAGEMENT
Cross-Team Sprint Portfolio Brief for Execs in Confluence
Weekly, an agent reads the active sprints across multiple Linear teams, weighs each team's risk and progress, writes a one-page executive portfolio brief.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly pre-review schedule fires
- ActionFetch active cycles across Linear teamsLinear
- LogicAgent assigns per-team risk rating
- ActionPublish portfolio brief to ConfluenceConfluence
- OutputEmail brief and link to leadershipGmail
What it does
Rolls many teams' sprints into a single executive view. An agent pulls each team's active cycle from Linear, judges progress and risk per team, and produces a one-page portfolio brief that flags which teams are on track and which need attention, then publishes and distributes it.
When to use it
When leadership oversees several squads and needs one trustworthy weekly read instead of chasing each lead. Best for orgs running parallel Linear teams where the value is the cross-team judgment, not raw numbers.
How it works
- 1A weekly schedule fires before the leadership review.
- 2The agent fetches the active cycle and issue health for each configured Linear team.
- 3It reasons over each team's completion, blockers, and trend to assign a risk rating.
- 4It writes a one-page portfolio brief highlighting at-risk teams and asks.
- 5Publish the brief as a Confluence page under the leadership space.
- 6Email the brief and Confluence link to the leadership distribution list.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect GmailRead, draft, send, label.
- 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.