From a Slack mention to a merged pull request

Most engineering requests do not start in an issue tracker. They start in a channel: someone from finance asks whether billing history could be exported, a support lead pastes a customer complaint, a designer notices a misaligned button. By the time that becomes a ticket, half the context has been lost.

The Slack integration exists to close that gap.

Step 1: mention it where it happened

Anyone in a connected workspace can mention @dispatcher in a channel or thread with the request in plain language. Dispatcher reads the message, along with the surrounding thread when there is one, and creates a task on your board.

It replies in the thread with the task title and a link, so the person who asked can see their request was captured and where it lives.

Step 2: shape it into a task

The new task carries the original request and a link back to the Slack thread. Before handing it to an agent, it is worth spending a minute turning it into a task an agent can finish: a clear outcome, a scope, and a definition of done. The original conversation stays attached, so nothing is lost in the rewrite.

Step 3: dispatch an agent

From the task, pick a harness and execute it. Dispatcher creates a branch and an isolated worktree, starts the agent there, and keeps its terminal next to the diff. Other agents working on other requests continue in their own worktrees, untouched.

Step 4: review

When the agent finishes, read the diff, run the tests, and either approve it or send it back with specific notes. Review happens in the same window as the terminal that produced the change, which makes "why did it do that?" a short question.

Step 5: ship

Approve and open the pull request from Dispatcher. If the change is large, ship it as a GitHub Stack of dependent pull requests instead of one big review.

Setting it up

Slack is connected per organization from Settings, then Slack, while signed in. Each workspace admin approves the app once; after that, mentions in channels the app has been added to create tasks for that organization.

What we deliberately did not build

We did not make Slack mentions start agents automatically. A mention creates a task; a person decides when an agent runs and what it is allowed to touch. Requests from a busy channel are exactly the ones that benefit from a minute of scoping before any code is written, and review stays mandatory either way.