Skip to content
Scopeleaf
Sign in
Get started

Use cases

One session. Six people at the table.

One feature, six rooms: each at the moment that matters to that person, with one thing to click.

Product owners

Product owners turn a rough idea into a ticket engineering can start.

Paste what you know. The first AI review shows what is missing, and every proposal waits for a person to approve it.

Select a vague criterion and ask for a testable one. Approve the wording your team can verify.

Try the editor, no account

APP-482MALEPRDraft

Pair a new device from the app

Summary

Users add a new device from the mobile app. The app finds the device, connects it to Wi-Fi and registers it to the user’s account.

Acceptance Criteria

  • Pairing starts from the Devices tab.
  • The app finds nearby devices within 30 seconds.

  • The feature must be verified on supported environments.

LE Leo asks Scopeleaf AI

Add to Acceptance Criteria that testing must happen on a physical device, not only a simulator.

The ticket APP-482 as a draft. Leo asks Scopeleaf AI to require testing on a physical device; the AI rewrites one acceptance criterion, marked as AI until someone approves it.

Product managers

Product managers answer the questions before engineers have to ask them.

GrillMe reads the draft and interviews the team in rounds: offline states, ownership, regions, the measure of success.

One question at a time. One operator answers for the team while everyone follows live, and a big question breaks down into the ones under it.

How GrillMe works

APP-482MALEPRGrillMe · question 3 of 9

Pair a new device from the app

Summary

Users add a new device from the mobile app. The app finds the device, connects it to Wi-Fi and registers it to the user’s account.

Acceptance Criteria

  • Pairing starts from the Devices tab.
  • The app finds nearby devices within 30 seconds.
  • The feature must be tested on a supported physical device. Simulator-only validation is not sufficient.
GrillMe · dependencyWhat happens if the Device Registration API is unavailable?
Assumption · never confirmed“Within 30 seconds” — has anyone confirmed that on real hardware?
The same ticket in the GrillMe room: three questions wired to the lines they are about. Opening the first one shows the nine smaller questions under it.

Architects

Architects see the system around the feature while the scope is still cheap to change.

The questions surface what product prose hides: the API another team is rewriting, the region call that comes first, the flow that already exists.

Each one lands in the document as a dependency beside the outcome, where engineering reads it, not in a thread nobody opens twice.

Invite your coding agent

APP-482MALEPR4 dependencies

Pair a new device from the app

Summary

Users add a new device from the mobile app. The app finds the device, connects it to Wi-Fi and registers it to the user’s account.

Dependencies

  • Device Registration API
  • Region service
  • “Add accessory” flow
  • Push notifications
The ticket with its Dependencies section, and the four systems around it: the Device Registration API, the region service, the Add accessory flow and push notifications. Each card lights the line it belongs to.

Scrum masters

Scrum masters run a refinement that ends with decisions.

Every conclusion from the interview arrives as a precise change to the ticket: approve, edit or reject it in front of the team.

Decided and open stay separate. The team marks the ticket ready, exports it and closes the session.

Roles in a session

Proposed changes6 of 7 decided

  • Define offline behaviourAcceptance Criteria
  • Add Device Registration API dependencyDependenciesApproved
  • Clarify supported regionsSummaryEdited
  • Correct inconsistent terminologyGlossaryApproved
  • Add success measureSuccessApproved
  • Log every Bluetooth packetEdge casesRejected
  • Expand reconnect edge caseEdge casesApproved
APP-4821 open question

Pair a new device from the app

Acceptance Criteria

  • Pairing starts from the Devices tab.
  • The app finds nearby devices within 30 seconds.
Seven proposed changes from GrillMe, six already decided and one open. Approving the open one adds its line to the ticket and the count reads eight decisions, no open question.

Stakeholders

Stakeholders click the feature before anyone builds it.

A prototype built from the document, shared behind a password link. Whoever asked for the feature opens it without an account.

One note on one screen changes one requirement, and the team sees the change in the same document.

See a prototype

APP-482MALEPRPrototype shared

Pair a new device from the app

Acceptance Criteria

  • Pairing starts from the Devices tab.

  • When the device is unavailable, the user can retry.

9:41 Prototype

Device unavailable

Sensor S2 stopped responding.

A phone with the prototype's Device unavailable screen and the ticket behind it. Sam, with no account, taps Retry and leaves a note; the ticket's offline requirement changes in the document.

Engineering

Engineering should not be the place where we first discover what the feature means.

Developers and their coding agents start from a feature that has answered its questions: context, criteria, edge cases, dependencies, a prototype, and the open questions named.

It goes where the work is tracked: Jira, Confluence, Google Docs, Google Drive, Markdown or HTML.

Get started

APP-482MALEPRReady for development

Pair a new device from the app

  • Why are we doing this?A third of new devices are returned unused; most returns say setup failed.
  • User problemSetup fails halfway, and there is no way back in.
  • ContextThe Devices tab. EU and US at launch.
  • Proposed behaviourIf the device drops, finish setup later.
  • PrototypeFour screens, with Sam’s note applied.
  • Acceptance CriteriaTested on a physical device, not only a simulator.
  • Edge casesThree failed reconnects: offer support.
  • DependenciesDevice Registration API v2, Platform team.
The prepared feature, ready for development, beside six destinations. Choosing one sends it there, and a coding agent's terminal reads the ticket.