Skip to content

Mobile Feat: AI rewrite #8871

@Combs7th

Description

@Combs7th

@claude - Let's update the Mattermost Product Documentation to reflect the end user mobile AI rewrite workflow captured via mattermost/mattermost-mobile#9280.

Scope & constraints

  • Review the PR directly as the source of truth and map every claim to explicit PR evidence.
  • Do not modify changelogs, upgrade notes, version archive, deprecated/removed feature pages, or unsupported legacy release content.
  • Keep this to one docs task only. This is a user-facing workflow update, not an admin or integrator change.
  • Match the existing style, tone, heading structure, and formatting conventions already used on the current docs page.
  • Important: Model the mobile update on the existing Web/Desktop “Rewrite messages with AI” documentation on the Send messages page. The goal is to make the mobile section feel like a parallel workflow with similar completeness and structure, not a separate standalone concept.

Required doc touchpoints

  • Update source/end-user-guide/collaborate/send-messages.rst
  • Review whether source/end-user-guide/agents.rst needs only a minor cross-reference; avoid expanding it unless the PR clearly requires it.

What to document
Update the existing Mobile subsection under Rewrite messages with AI so it is comparable in usefulness and detail to the existing Web/Desktop subsection. Based only on PR evidence, document:

  • how a mobile user opens AI rewrite from the message composer
  • how the user selects from predefined rewrite actions
  • how the user uses a custom prompt, if supported by the PR
  • how the user selects an agent when multiple AI agents are available
  • what happens while the rewrite is being processed in the composer
  • how the user reviews and continues with the rewritten result before sending

What not to do

  • Do not create a brand-new top-level AI rewrite page.
  • Do not add admin setup/configuration beyond what is already documented unless the PR explicitly changes it.
  • Do not invent mobile-specific limitations, behaviors, or UI labels not visible in the PR.

Execution guidance

  • Start by comparing the existing Web/Desktop and Mobile rewrite content in send-messages.rst.

  • Use the Web/Desktop subsection as the documentation pattern to mirror for mobile:

    • similar level of detail
    • similar step ordering where applicable
    • similar action-oriented phrasing
    • similar treatment of choosing an agent, rewriting, reviewing, and sending
  • Keep the mobile instructions concise, but complete enough that a reader can follow the mobile workflow without guessing.

  • Prefer updating the existing Mobile bullets/steps rather than adding a large new section, unless the surrounding page structure clearly calls for it.

Output requirements
Provide:

  1. The exact page(s) to update
  2. A short explanation of the documentation gap being closed
  3. The proposed before/after change summary
  4. Draft doc text that fits the current page style
  5. A note on whether source/end-user-guide/agents.rst needs any change; if not, explicitly say no update is needed there

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions