> For the complete documentation index, see [llms.txt](https://help.metaforms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.metaforms.ai/review-collaboration/the-agent-review-pm.md).

# The Review Agent

The Review Agent runs automatically as soon as the questionnaire is opened — there is nothing to trigger. It runs five specialised reviewers together — **language, logic, data quality, programming feasibility, and methodology** — then consolidates and de-duplicates the findings, verifying each against the live document before presenting it.

![Accepting a suggestion, jumping to the edit, and seeing it in the Changes tab](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2FzxXug9NkMlqBtS5hX2fg%2Freview-demo-v2.gif?alt=media)

## Two kinds of suggestions

**Concrete fixes** propose a clear, specific correction. You get **Accept** (applies it as a tracked change), **Dismiss**, or **Add as comment**.

**Design suggestions** are judgment calls with no single correct fix — for example, *"confirm n=50 is sufficient for the intended analysis"*. You get **Add as comment** or **Decline**. There is no Accept, because a person needs to weigh in before anything changes.

![Adding a design suggestion as a comment, replying in the thread, and sharing it with the client](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2Ft2U4PFujbC4hAYnErflQ%2Fadd-as-comment-demo-v2.gif?alt=media)

{% hint style="info" %}
If a suggestion has no Accept option, that's not a bug — the finding needs a human decision, not a mechanical fix. Route it to whoever owns that call (often the client) via a comment.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.metaforms.ai/review-collaboration/the-agent-review-pm.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.