Anyone with an idea and a Claude tab can put work on the sled.
Most people in a company never had a ticket seat and never will. They have Claude or ChatGPT and they are making things all day: a spec, a prototype, a customer's request, a markdown file. Intake is the front door for them. From the conversation they already have open, they say what they want and what it is worth, and it lands sized, understood, and routed, with a receipt when it comes back.
Your AI asks the questions a good engineer would ask. Then it files.
A paragraph, a spec, a Loom, a Figma frame, a screenshot of a competitor. Your AI reads it first and only asks what it cannot answer from what you sent.
A conversation carries what a ticket never did.
A form gets a title and a guess. A conversation with your AI gets the reason, the people waiting, the deadline, the evidence and the code it touches. Every one of those is something smart routing uses.
One map per repo, rebuilt on every merge. The request says which areas it touches and which rows on the board it collides with, and the filer can correct it. That's what points smart routing at the people with history in that code.
Specs, prototypes and screenshots go on the row as files, up to 24 per row, so anyone on the board opens them in one click. About a page that exists? Your AI asks for its URL and a screenshot, and can mock the change in your design system.
Intake asks how many have asked. Three accounts beats one hunch, and smart routing knows it.
"Before their review on the 15th" becomes a due date on the row, so timing enters the routing.
Worth is asked, never guessed, and marked with who said it. Blank stays blank.
A question from the engineer's terminal lands in the filer's chat and as a Slack DM. They reply with a date, a number or a word, and it goes on the record.
Anyone added to the workspace connects from claude.ai or ChatGPT with their work email and can file, answer and check status. Seats are for the people who take the work.
Who builds is changing. We serve the seam.
Business users are moving toward engineering: writing the spec, building the prototype in Make or v0 or Bolt, filing the request with the repro. Engineers are not moving the other way. The builder tools make the business user productive on their own; the coding agents make engineers productive on theirs. The seam between them is where the cost and the hand-off are, and it is where nothing sits.
Intake is what sits there. Someone asks the questions a good engineer would ask; someone turns the answers into a shape an engineer can size without losing the why; and the engineer who takes it sees that why first, because understanding the work is the part of the job that grows as the typing part shrinks.
The why travels with the row.
Stored on the row, shown to the engineer at pickup, and returned to you with the receipt. Every field says where it came from: your words, the artifact, or the product map. An engineer never picks up a row without it; a brief without a why is a draft.
Two verbs close the loop without either person leaving their surface. Ask the filer: one question from the engineer's terminal goes into your thread; your AI answers from context if you already said it, and asks you only when it cannot. The receipt: back to your thread when it lands.
Same conversation, whichever AI they use.
Wherever it starts, it lives in one place.
Claude or ChatGPT with the connector added once. "Send this to engineering" with a file, a link or a paragraph. The primary door.
A plugin bundles the connector, the "send to engineering" skill and the spec template, so the business side installs in one line too.
/sled intake: an engineer filing for themselves or a teammate. Same tool, same questions.
Message the sleds app or /sled intake …. Same thread, in a DM.
sleds.ai/i/… for the person with a Figma link and a browser. Opens the thread by email.
An issue labeled intake becomes a thread; the brief lands back as the body.
Add one connector. Every verb, in the conversation.
Add mcp.sleds.ai/mcp as a connector in Claude, ChatGPT, Cowork or Claude Design and sign in with your workspace account. From then on the same verbs the engineer has in the terminal answer in your conversation.
Your AI runs the conversation under instructions we serve it. sleds enforces the parts that matter at the boundary: the brief is a schema, worth is marked by who said it, the filer is the signed-in identity, nothing is written before "yes". It works the same whichever AI is on the other end.
https://mcp.sleds.ai/mcpclaude · chatgpt · cowork · claude design · sign in with your workspace account
| say | get back |
|---|---|
| intake {text, links, file} | The questions, then the brief for confirmation. On "yes", a row. |
| touches {question} | What it touches in the product map, and what on the board collides. |
| attach {row, file} | A spec, prototype or screenshot on the row, for anyone on the board. |
| estimate {spec} | A band, a fit, a confidence, a cap. Recorded. |
| dispatch {spec, worth, links} | A row on the board, priced, with a suggestion. One paragraph. |
| status {row} | Who has it, what it has cost against the band, what is waiting on you. |
| answer {question} | Your reply to engineering's question, on the record. |
| handoff {task, to} | Parked for a named teammate or buddy, with the brief. |
| pickup {id} | Work someone sent you, back verbatim, running on your seat. |
| usage | Your meter: bars, credits, the reset, what is queued. Yours in full. |
| help {word} | The whole table, filtered. Chat, terminal and app never disagree. |
Your AI asks. People decide.
| rule | what it means |
|---|---|
| Asks; never decides | You confirm the brief; the lead adjusts worth on the board; the policy dispatches. Nothing is filed before "yes". |
| Worth is asked, never guessed | Blank stays blank. A missing worth is never a low. |
| You stay the requester | Your name on the row, your thread for questions, your receipt at the end. Nothing is filed as sleds, nothing as the model. |
| The why travels with the row | An engineer never picks up a row without the brief. |
| Free for everyone | No seat to file. A seat is needed to take work, not to request it. |
Add the connector.
Intake is part of every workspace. Request an invite and we'll set yours up, connector included.
https://mcp.sleds.ai/mcp