When
Launch brief
A Slack message in #launches kicks research, a draft, a reviewer, then a Notion page waiting for you.
Workflows
Draw the path once. Run it every time.
A workflow is the spine of the bench: a trigger, a sequence of agents, a human gate where it matters, and a place for the work to land. Save it. Name it. Run it on Monday again.
TriggerSlack :memo:
ResearcherBrief
WriterDraft
ReviewerFlags
→
Human gateYou
→
PublishNotion
Recipes on the shelf
Start from a path people already run.
Copy a recipe into your workspace, swap the agents, keep the gates.
When
Support triage
New ticket in Linear. Ops agent labels it, drafts a reply, and parks it for a human if the tone is hot.
When
Weekly digest
Friday 3pm. Pull GitHub and Linear, write a one-pager, drop it in Slack — no meeting required.
When
Call notes
Zoom ends. Transcript in, summary out, tasks into Asana, follow-up mail sitting in drafts.
The pieces of a path
Triggers, steps, gates, landings.
01
Triggers
Schedule, webhook, Slack reaction, new file, new issue. The path starts from a real event.
02
Steps
Each step names an agent and the tools it may use. Output is a packet the next step can read.
03
Gates
Approve, edit, or send back. Gates are people, not a checkbox buried in settings.
04
Landings
Notion, Drive, GitHub comment, Slack thread. The work ends in the open, not in a chat you lose.
Ready