Product

Ask PM in comments

Mention @pm in a comment on a feature's or a component's specification, on a knowledge-base document, or in Marketing on a Marketing release's public release notes, one of its blog posts or a customer's email, and the PM agent answers in the thread. It reads the passage you highlighted, the thread and the document, and looks up what else your question needs in your workspace: the knowledge base, features, applications and feature requests.

When the thread asks for a change:

  • On a highlighted passage, PM changes that passage right away, in the document everyone is looking at. Its reply says what it changed, and Undo beside it puts the old text back.
  • On a general comment (one on the whole document), PM suggests a change, and the suggestion opens in Review changes like any other draft. Nothing changes until someone applies it.

PM answers one thread of a document at a time, in the order you asked, so two requests never change the same document at once.

On a feature or a component, you can also switch on Code access: a read-only coding agent then answers instead, from the feature's code.

Key concepts

PM thread. A comment thread whose first comment mentions @pm. Every reply anyone writes there goes to PM, with or without @pm. The thread card says Asked PM, and its reply box says Reply to PM....

Asking in another thread. In any other thread, only a reply that mentions @pm reaches PM. The other replies stay between people.

Highlighted passage. The text you selected when you wrote the comment. PM changes only the paragraphs, headings, list or other blocks that text is in, nothing else in the document. After its change, the highlight covers the text PM wrote.

Suggestion. A change to the whole document that PM proposes from a general comment. It waits in Review changes, where you apply it block by block or dismiss it. Applying it resolves the thread it answered.

The line. When several threads on one document ask PM, it answers them one at a time, oldest request first. A thread waiting its turn reads Queued, 2nd in line.

Code access. A read-only coding agent answers the thread from the code of the feature's linked applications. It runs as a coding session, charged as a coding run.

Asking PM

To ask PM about a passage

  1. Open the feature, the component, the knowledge-base document or the Marketing document.
  2. Select the text you want to ask about. On a document you can edit, choose Comment in the menu that opens below it, or turn on Review mode first.
  3. Type @ and choose pm ("Ask PM about this document"), then your question or request: for example, "make this shorter" or "mention Apple Pay too".
  4. Choose Comment.

PM starts as soon as it is free on this document. The thread stays open beside the document, and PM's row in it shows Waiting for PM (or Queued behind another thread), then Thinking, at its right edge until its answer appears. To stop PM, point at Thinking and choose Stop.

When you asked for a change, the passage changes in front of you and in every open copy of the document. You can keep typing elsewhere in it meanwhile: nothing you write is lost.

To ask PM about the whole document

  1. Choose Add a general comment, at the top of the comments beside the document.
  2. Type @, choose pm, and write your question.
  3. Choose Comment.

A change asked here comes back as a suggestion in Review changes.

To ask with Code access

  1. Write a comment that mentions @pm, on a feature or a component.
  2. Switch on Code access beside Comment.
  3. Choose Comment.

PM's row reads Reading the code in SSID-n while the coding agent works. It replies in the thread, and suggests a change only when the thread asks for one. Code access is off by default. In a reply, it starts on whatever the thread's last answer used.

To follow up

  1. Reply in the thread. In a PM thread, any reply goes to PM. Elsewhere, mention @pm.

PM answers what was written since its last answer, with the whole thread in mind. A reply written while PM is answering, or while the thread waits in line, joins the next answer without losing the thread's place.

To undo PM's change

  1. Choose Undo, beside Edited on PM's reply.

The passage reads as it did before PM changed it, and the reply shows Undone. Undo works while the passage still reads as PM left it: once someone has changed it again, edit it by hand instead.

To review PM's suggestion

  1. Choose Review changes, beside PM's reply. The header says Suggested by PM in a comment thread.
  2. Choose Reject on any change you don't want, or Edit to rewrite it.
  3. Choose Apply, or Dismiss.

Applying the suggestion resolves the thread. Dismissing it leaves the thread open, so you can refine your request and ask again.

To stop PM

  1. Choose Stop on the thread card.

PM stops, and the card reads PM couldn't answer: it was stopped. with Ask again. The next thread in line starts.

Thread states

The card showsWhat it means
Waiting for PM on PM's rowThis thread is next: PM starts from any open copy of the document.
Queued, 2nd in line on PM's rowPM is answering another thread on this document first.
PM hasn't started. and Ask againNobody had the document open for a day after you asked.
Thinking on PM's row (point at it for Stop)PM is answering.
Reading the code in SSID-n on PM's row (point at it for Stop)With Code access, the coding agent is reading the code.
PM's reply, with Edited and Undo beside itPM changed the highlighted passage.
PM's reply, with Undone beside itSomeone undid PM's change.
PM's reply, with Review changes beside itPM answered a general comment, and suggested a change.
PM couldn't answer: the reason, and Ask againThe answer failed or was stopped. Ask again puts the thread at the end of the line. With code access asks again from the code, where it's offered.

How PM behaves

PM changes only what you highlighted. On a highlighted passage, it changes the blocks your highlight touches and nothing else. When you ask for more, it says so and asks you to highlight the text you want changed, or to ask in a general comment.

PM changes a document only for someone who can edit it. When the person who asked can comment but can't edit, PM describes the change in its reply instead.

One at a time per document. PM answers the threads of a document in the order they asked. Any open copy of the document starts the next one, so you don't have to stay on the page; PM answers as the person who asked, with their access. If nobody has the document open, the request waits until someone opens it.

PM looks beyond the document. When your question reaches past the document, for example which features it relates to, which application builds it, what customers asked for or what your knowledge base says, PM looks it up before it answers, with the access of the person who asked. Its reply links what it used: choose a link to open that feature, application, feature request or knowledge-base document.

Everyone on the document reads PM's reply. PM looks things up with the asker's access, and its reply is visible to everyone who can read the document's comments. It can mention something, such as a private feature or a customer's name, that only the person who asked can open.

PM never resolves a thread. A person resolves it, or applying PM's suggestion does. After a direct change the thread stays open, so you can follow up or undo.

One suggestion at a time. While a draft of the document waits for review, from a scan, Review mode or another general comment, PM can't suggest a second one. It says so in its reply. Changes to a highlighted passage aren't held up by a waiting suggestion.

PM threads aren't sent by Review mode. PM already answers them, so Review mode's Send to agent leaves them out, and its count doesn't include them.

Documents synced from a repository take no changes: PM discusses them and says so.

In Marketing, PM writes for your customers. On customer release notes, a blog post or a customer's email, it writes in plain benefit language, with no internal-only work, no customer named in public copy, and nothing the document or the thread doesn't say. An email keeps its greeting and sign-off. When your request is unclear, it asks in the thread before changing anything. While Productmind is writing a new draft of the document, PM can't change it, and says so. A change to a customer's email makes it an email you edited, and a change to published release notes is an unpublished change until you publish again.

What it costs. Each answer from PM uses AI credits, like a message to the PM agent. An answer with Code access runs a coding session, charged as a coding run, the way Review mode's Send to agent is. See Usage.

Permissions

ToYou need
Ask PM, and reply to PMComments: Create, and the PM agent: Chat: Create and Chat: Update
Have PM change a highlighted passageTo be able to change the document. In Marketing, Marketing: Update
Undo PM's change, or apply its suggestionTo be able to change the document. In Marketing, Marketing: Update
Ask with Code accessAlso Features: Update (Can edit on a private feature) and Sessions: Create

Troubleshooting

@pm isn't in the list

Your role doesn't include the PM agent, or you can't comment on the document. A mention you type by hand is then plain text.

Code access is missing

You're on a knowledge-base document, or you can't edit the feature or start coding sessions.

Code access needs code to read. Link an application with a repository to the feature, or ask without Code access.

PM says the highlighted passage is no longer in the document

Someone deleted or rewrote the text your comment was on before PM started. Highlight the text as it reads now and ask in a new comment.

"The passage changed since PM's edit"

Someone changed the passage after PM did, so Undo can't put the old text back safely. Edit it by hand, or ask PM again.

PM hasn't started

Nobody had the document open for a day after you asked. Choose Ask again.

Last modified on