Ticket Scoping

  • Desktop app
  • All plans
View as MarkdownFeature page

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 In Progress, never notifies the reporter that work began, never writes a file and never commits.

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, with the Product Manager avatar and a lightbulb badge, sits in the ticket modal. It only appears on feedback tickets.

How to use it

  1. Open the feedback ticket and click Scope this idea. The board hides, the scoping agent's terminal opens with the framing brief already sent.
  2. The agent explores the codebase and builds the mockup, then publishes it. The mockup card appears in the ticket's Conversation with the reporter block, marked internal.
  3. Click Open the mockup to review it in your browser. Refine by talking to the agent if needed.
  4. Click Share to client on the mockup card. 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.
  5. 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 (Settings > Defaults > Scoping Agent; project override in Project settings > Default agents): 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: true is only used when you explicitly asked to send it to the reporter.

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 only: the mockup bubble with Yes, that's it / Not quite is in the phone's Your feedback thread, same words as the desktop. Launching a scoping and sharing the mockup are desktop actions, where the agent runs.

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 to 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.
  • 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