Here is the most expensive sentence in software: "I'll ask product and get back to you." It means the engineer stops. The context in their head starts to decay. They write a message, the PM is in a meeting, the answer arrives at 4:40, and the work resumes tomorrow morning with half the context rebuilt from scratch. If an agent was doing the work, it is worse: the session ends, and the next one starts cold.
The feature was never the hard part. The question in the middle of it was.
What happens now
When an engineer, or the agent running a node, hits something the brief does not settle, they do not leave. They park the item with a decision: the question, two or three options, and what each one means. On a route the engine writes this itself when a node cannot continue; from Claude Code it is one line, /sled ask.
The decision lives on the item, and the item reaches the person who can answer it wherever they are. In Slack, the SLEDS app posts the card in the thread where the request was filed, with the options as letters. In Claude, the connector shows the same card to the requester in their next message. On the board, the row says needs you and only to the people it needs. In the menu bar, the Need filter lights up for the engineer.
The requester taps a letter. The engineer sees the answer on the item, in the terminal if they are in one, and the agent resumes with the answer in its pack. Nothing was re-explained. Nothing was scheduled. The decision stays on the row with a name and a time, which is the first time most teams have had that record at all.
Why this needs the integrations, not just the app
The whole trick is that the question goes to where the answerer already is. Product managers do not watch a board. Support does not open a tracker. The founder is in Slack and Claude and nowhere else. If answering required opening sleds, the question would wait, and waiting is the cost we are removing.
So the Slack app, the Claude connector, the Cowork plugin and the GitHub App are not conveniences around the product. They are the product's way of reaching the person with the answer, in the one channel where they will see it in the next ten minutes.
One week, one team
On one team running this for a month, what the engineers reported was not fewer questions. It was the same questions, almost none of them in a meeting, and most answered before the context in their head had gone cold. The work that used to pause overnight paused for the length of a coffee. That is the gap closing from the engineering side, the same way intake closes it from the business side.