Automate Slack workflows.
Every team runs the same leaky loop: someone reports a bug in a Slack thread, it collects three thumbs-up, and then it evaporates before anyone files it. Off-the-shelf Slack-to-Linear connectors exist, but they're rigid, they map fields you don't control, and they meter you per task run. When the glue between them is fifty lines of Bolt.js, renting it monthly is absurd. This blueprint builds that glue as code you own.
A Slack bot built on Bolt.js that listens for a /ticket slash command. When a teammate types it, the bot opens a Slack modal, a small form for the issue title and details, and on submit it calls the Linear API to create a new issue. The interactive path is wired end to end: slash command registration, the modal view, and the submission handler that turns what someone typed into a real Linear ticket without anyone leaving Slack.
You watch it happen in the task workspace: the agent scaffolds the app, wires the command, the modal, and the Linear call, then runs the handler against a test submission to confirm an issue is created. The code lands on a branch in your repository with a pull request ready.
The first version is a foundation you steer with plain follow-up messages:
Each follow-up wakes the same repository and the agent continues on its own code.
Do I need Slack admin rights? You'll create a Slack app and install it to your workspace; the agent scaffolds the bot and tells you exactly which scopes and tokens it needs.
Does this replace Linear? No, it's a fast lane into Linear. Issues are created through its API and live there as usual, this just skips the context switch.
Can it target something other than Linear? Yes, the pattern is the same for Jira or GitHub Issues. Ask the agent to swap the create-issue call and it rewires it.