The situation
Your agent wrote the first draft of a product spec from a Slack thread and two tickets. Before anyone builds it, product, engineering and design each need to poke at it. A shared doc works when everyone lives in the same suite. It does not work when the designer is a contractor, the engineer refuses to open the doc tool, and half the comments end up as screenshots in chat.
What you say
You, to your agent
Publish the saved-searches spec to PTAL and give me a link for Ana, Raj and Lee.
The spec is Markdown, so it renders as it is. The page goes to the three of them in whatever channel they use. If your team is on Pro, the agent can limit the page to members of your organization so a forwarded link goes nowhere.
What reviewers see
The spec as a readable page, with a count of notes in the corner. Ana selects “about 40 tickets a month” and corrects it to 62. Raj selects “per user, in local storage” and explains why that will not sync across devices. Lee selects “as a dropdown in the header” and suggests the sidebar. Each of them sees the others’ notes, so Raj and Lee do not both write the same thing. Signed-in reviewers appear by name and photo.
What comes back
You, to your agent
Any notes on the saved-searches spec?
- Ana on
40 tickets a month
: “Update this: it is 62 after the September release.” - Raj on
per user, in local storage
: “Local storage won’t sync across devices. Store server-side; it’s one table.” - Lee on
as a dropdown in the header
: “Header is full. Sidebar section, collapsed by default?”
The agent proposes an edit for each, you say yes, and it publishes version 2, replies on the threads with what changed, and resolves them. The next reviewer who opens the link sees version 2 with zero open notes, and can still flip back to version 1.
Why it works here
- Notes point at sentences. The agent gets the quoted text with every comment, so “this is wrong” is never a mystery.
- Reviewers see each other. Comments are threaded on the page. Nobody duplicates, and the agent can reply where the question was asked.
- Markdown in, page out. The spec stays a file in your repo. The agent publishes it; nobody pastes into a doc tool.
- Versions are the changelog. Every publish is a numbered version at the same link, with restore.
- Contractors included. A reviewer outside your organization can comment without an account, or you can require sign-in for everyone.
Comments come back over the inbox API, as a Markdown digest, or through the MCP connector if your reviewers’ questions should go to ChatGPT or Claude on the web instead.