Ticket Scoping
- Desktop app
- All plans
What it does
Adds a framing step to a feedback ticket before anyone builds it. One click spawns a temporary Product Manager agent that reads the project's codebase, works out which surface the request touches and what the product looks like, then produces a single self-contained HTML mockup of your real product with the requested change applied. The preview link comes back to you first; you decide whether to share it with the person who reported the idea, who answers in one tap from their in-app feedback chat. Scoping never starts the task, never moves the ticket to Development, never notifies the reporter that work began, never writes a file and never commits.
Video (1 min 25): Ticket Scoping, shown in the real app. A client asks for "a button somewhere on the product page", one click on Scope this idea starts a Product Manager agent that reads the shop's code, and the mockup of the shop's own page, with a heart on every product, waits on the request for review before it is shared.
Where to find it
Open a feedback ticket on the Backlog (a ticket that came from the public backlog, the widget, the Chrome extension or the support chat). The Scope this idea button is an icon button with the Product Manager avatar and a lightbulb badge, in the bottom bar of the ticket modal, next to Cancel (its label shows in a tooltip on hover: "Spawn a Product Manager agent that builds a mockup to validate the idea with the person who reported it, without starting the task or notifying them."). It only appears on feedback tickets, which show a Client feedback block at the top of the modal.
How to use it
- Open the feedback ticket and click Scope this idea. The board hides, a new agent named "Scoping: <ticket title>" appears under Working in the sidebar, and its terminal opens with the framing brief already sent.
- The agent explores the codebase and builds the mockup, then publishes it (about three minutes on a small project) and prints the mockup link in its terminal. Reopen the ticket: the Conversation block now holds a Scoping mockup v1 card, "Published for review. The client has not seen it yet.", with Open and refine and Share with the client.
- Click Open and refine on the mockup card: the mockup opens in the Mockup studio, inside the app. To change something, click Point at an element, click the element in the mockup and write what should change; add as many changes as needed, or Add a general note. Then click Refine the mockup: a scoping agent takes that exact version, applies only your changes and publishes the next version (v2, v3…) on the ticket. The request is also kept in the ticket's internal Comments. The version chips at the top of the studio switch between versions; Open in the browser is in the studio header.
- Click Share with the client on the version you want (on its card, or in the studio header). The reporter receives it in Your feedback with the question "Does this match what you had in mind?" and two buttons, Yes, that's it and Not quite; the answer lands as a normal comment on the ticket.
- Once the idea is validated, start the same ticket as usual: the framing is already in its conversation.
Comment on the ticket to ask a clarifying question: the message reaches the reporter's chat and their reply comes back in the same thread.
Settings
- Scoping Agent profile (
scopingAgentProfile, Settings > Defaults > Scoping Agent; project overridescopingAgentOverridein Project settings > Default agents; both readable and writable withsettings_get/settings_set): which role, provider and model frame the idea. "Not set, follows the ticket's executor" by default, meaning the scoping runs on whatever CLI the ticket's assigned agent uses.
Agent tools (MCP)
backlog_publish_mockup: publishes the HTML mockup on the ticket and returns the preview link. Internal by default;notifyClient: trueis only used when you explicitly asked to send it to the reporter.refinedFrommarks a refined version.backlog_get_mockup: reads the HTML of a published mockup (the latest one by default), so a refine run edits the current version instead of starting over.
Providers
Runs on the provider of the Scoping Agent profile, or of the ticket's executor when no profile is set. Documented as working the same on Claude, Codex and Antigravity; the mockup itself is plain HTML, so nothing depends on the CLI.
Mobile
Reporter side: the mockup bubble with Yes, that's it / Not quite is in the phone's Your feedback thread, same words as the desktop.
Owner side: in the ticket's conversation, each mockup is a card with Open mockup, Share with the client, and a field to describe a change followed by Refine. The phone does not run the agent: the request goes to your computer, which starts the same refine agent as the studio (the project must be open on that computer). Pointing at an element is desktop only. Launching the first scoping stays a desktop action.
Limits
- Feedback tickets only; a ticket you created yourself has no Scope this idea button.
- The mockup must be self-contained (inline CSS and JS, no external resources) and is capped at 2 MB. It is a static visual proof, not a working feature.
- The mockup is stored on the ticket as soon as it is published, but stays invisible to the reporter and to the public page until you share it.
- The two answer buttons are shown to the reporter only while the mockup is the last message of the thread.
Common questions
- Is the mockup sent to my client automatically? No. It comes back to you, attached to the ticket, and goes out only when you click Share with the client.
- Does scoping start the ticket? No. Status, notifications and files are untouched; the ticket is started separately once validated.
- Which agent does the scoping and can I change it? A Product Manager by default. Set a Scoping Agent profile globally or per project to choose the provider and model.
- Can I change the mockup without starting over? Yes, with Refine the mockup in the Mockup studio (or Refine on the phone): the agent edits the version you looked at and keeps everything you did not comment on.
- How do I turn a vague feature request into a mockup? Open the feedback ticket, click the Scope this idea button (Product Manager avatar, bottom bar of the ticket), wait for the agent to publish, then open the Scoping mockup card with Open and refine. The video shows it: https://youtu.be/2JlgCR1l_VY
- Is there a video that shows it? Yes, a 1 min 25 demo in the real app: https://youtu.be/2JlgCR1l_VY
- Why does the mockup look like my product? The agent reads your codebase first and reproduces the surface it identified, instead of a generic wireframe.
Related
- Public Remote Backlog: where feedback tickets come from.
- Feedback & Support Chat: the reporter's Your feedback thread where the mockup and questions arrive.
- Backlog Task Board: the board the ticket is executed from afterwards.