Intent on every mark
Must-fix, nice to have, question, or keep — so the agent knows priority without another meeting.
Built for Product
Open the review link, mark must-fix vs nits on the capture, and invite stakeholders on a guest link. No MCP install for product or clients.
Product feedback in Slack and docs rarely maps to pixels. Stakeholders pile on in threads while the agent waits for a clear brief — and guest opinions can blur into decisions if roles are fuzzy.
Open `/r/{token}` from engineering or design. Mark must-fix items first, questions where you need clarity, and keep where scope should not change. Share a guest link for PM/client eyes; accept their suggestions only when you want them authoritative. Approve or request the next pass.
Must-fix, nice to have, question, or keep — so the agent knows priority without another meeting.
Clients and partners leave suggestions. They stay non-authoritative until the review owner accepts them.
Only the review owner approves, requests changes, or verifies. Product can own the link without running MCP.
Request changes when the bar is not met. Track open → resolved → verified so nothing gets lost between releases.
Turn a vague “doesn’t feel right” into work the agent can follow.
Try saying these to your agent after connecting MCP from the homepage.
No. Reviewers and product owners only need the review link. Engineering connects the agent.
Stakeholders who should suggest without owning approve / request-changes. You accept suggestions into marks when ready.
Use must-fix sparingly, mark keep on intentional choices, and request a new pass instead of endless chat edits.