Slack is where the business already talks about what it wants. The question was never whether sleds should be in Slack; it was how much of it should be. The answer we landed on: everything a person needs in the moment, and nothing that belongs on the board.
In a thread
Mention @SLEDS in a channel or a thread and it reads what is above it. A customer complaint with three replies becomes a draft request with the why already filled in, and it asks, in the thread, the one or two things it still needs. "Yes" files it. The thread stays linked to the row, so the people who were talking are told when it is sized, when it starts, and when it lands, without anyone writing the update.
DM it and the same thing happens privately. Most support desks use the DM; most product managers use the channel, because the channel is where the evidence is.
Answering
When a node parks with a question, the card posts in the thread the request came from, options as letters. Reply with the letter. The build resumes. The person answering did not have to know what a node was.
The roll-up
Once a day, or whenever you ask, a channel gets the roll-up: what landed and what it cost against the band, what is waiting on someone and for how long, what has no worth stated yet. Leads adjust worth on a row from the thread. It is the only status report, and nobody wrote it.
What it will not do
It will not let you edit a filed request's brief from Slack; that happens on the item, where the change is recorded against the row. It will not post to a channel it was not asked into. It never posts the contents of a PR, a stack trace or a prompt; the card says what moved and links to the row. Slack is where people are. The record is somewhere quieter.