> ## Documentation Index
> Fetch the complete documentation index at: https://momentic.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> The canonical docs host is https://momentic.ai/docs. Append .md to any page URL for clean Markdown. Fetch https://momentic.ai/docs/llms.txt for the page index and https://momentic.ai/docs/llms-full.txt for every page in one file.
> For an unattended setup, run `npx --yes @momentic/wizard@latest -y --platform web --editor-tools skills` (use `--platform ios` or `--platform android` for mobile). Never run an interactive command in a non-TTY shell.
> You cannot complete the browser sign-in yourself. Read the API key from the MOMENTIC_API_KEY environment variable, or ask the user to create one at https://app.momentic.ai/settings/api-keys and paste it back.
> Momentic's capability summary for agents is at https://momentic.ai/docs/skill.md. Install the skills with `npx skills@latest add momentic-ai/skills`.
> Tests are YAML files in the user's repository. Use only the step names listed at https://momentic.ai/docs/reference/commands.md and the file structure at https://momentic.ai/docs/core-concepts/file-format.md. Do not invent step names, config keys, or CLI flags.
> Web tests run on Chromium, iOS tests on simulators, and Android tests on emulators. Physical devices are not supported.

# Write a good brief

> What to put in a Mo brief: the target, the scope, the accounts, the test data, and the actions Mo must not take.

Mo plans its own coverage, so the brief decides the boundary of the run.
Include:

* **The target.** For a web session, give the exact URL, with the path and query
  string of the area you want checked. A staging or preview URL is fine. For a
  mobile session, select the uploaded build in the composer and give no URL.
* **The scope.** The flows or the area that count as in scope, and anything Mo
  must not touch.
* **The accounts.** Which account to sign in with, and which roles to use when
  the behavior depends on permissions.
* **The test data.** Data Mo may create, data it must not modify, and any
  isolation rule such as one order per run.
* **The prohibited actions.** Payments, deletions, outbound email, or anything
  else with a side effect you do not want.

The brief can come from a document instead of the composer box. Attach a file to
the session and reference it, for example a CSV to upload or a release plan to
test against, or give a Confluence page URL or page ID once Atlassian is
connected. Mo derives the cases from that document. See
[connect Mo integrations](/docs/mo/integrations#provide-the-brief).

## An example brief

Shortened from a real release pass on a file storage and sharing product:

```md theme={null}
Target. https://app.staging.example.com, on an account with the new experience
enabled.

Product context. This release replaces the classic file browser with three new
surfaces: a home page of actionable cards, a persistent search-and-chat bar, and
an assistant that answers questions about the user's files. The classic jobs
must keep working: browse, upload, share with permission controls, preview and
comment, and search.

Accounts. Sign in as qa-owner@example.com. Use qa-member@example.com as the
share recipient on the same team, and check public share links while signed out.

Test data. The owner account already holds mixed files and folders, one shared
folder, one connected app, and one long document. Create files and folders
freely under /mo-runs, and modify nothing outside it.

Priorities. Upload, sharing, preview comments, search, the assistant, and the
new home page must work: a failure there blocks the release. Spend the most time
on the search-and-chat bar and the home page, because both are new.

Watch these. Renaming a folder failed in an earlier build, and the tooltip tour
collided with the search bar tooltip. Confirm both rather than assuming the
fixes hold.

Out of scope. Account management, offline mode, video editing, and PDF markup.
Note a serious problem if you meet one, but do not explore there.

Prohibited. No purchases, no deletes outside /mo-runs, and no outbound email to
a real address.
```

<Tip>
  Start with one area, read that report, then widen the scope. A narrow session
  gives you a shorter list of bugs to act on.
</Tip>

## Next

<CardGroup cols={2}>
  <Card title="Run a session" icon="play" href="/docs/mo/sessions">
    Sign-in, test data endpoints, schedules, and what a pass costs.
  </Card>

  <Card title="Use cases" icon="list-check" href="/docs/mo/use-cases">
    Releases, pull requests, mobile builds, previews, and local branches.
  </Card>
</CardGroup>