Product demos & UI / Prompt

Prompt: show a comment becoming a resolved discussion

Track a single comment thread through a clear reply and resolution. Keep the author of each action visible and avoid equating a resolved discussion with whole-project approval.

By AnimroUpdated 2 min readAI-assisted · independently agent-reviewed

Who this is for: Teams demonstrating comments and review conversations.

What to prepare

  • Thread state sequence
  • Matching text revision
  • Role and resolution behavior

Copyable creative brief

An authored planning example. Replace illustrative details with your approved product facts and assets.

Plan a 30-second illustrative collaboration demo for sample document D-014. Example reviewer comments, “Clarify the opening instruction.” Hold the comment beside the relevant passage. Switch explicitly to Example author, who revises the passage and replies, “The opening now names the first action.” Use supplied product states to show that revision and reply; do not invent real-time collaboration. Switch to the role permitted to resolve the discussion and activate the verified Resolve action. End on the same thread’s resolved state while D-014 remains identifiable. Show author labels with each message. Use “Discussion resolved” as the closing line, not “Document approved,” unless a separate actual approval action is demonstrated. All content is fictional and illustrative.

Make it your own

Object
Use one stable document identifier and passage.
Comment and reply
Make the response address the original request directly.
Resolver role
Identify the actor authorized by the actual workflow.

Prepare the thread evidence

Supply the comment, affected text, revision, reply and resolved view. Keep the message order consistent. If the product hides resolved threads, show the documented way to inspect the result rather than manufacturing a permanent badge.

Adapt the review

For an introductory cut, show one concise revision and one reply. For training, explain who can resolve the thread and whether it can be reopened. Add only behavior that the supplied workflow confirms.

Fix author confusion

If the same avatar performs all actions, add explicit account transitions or use correct separate captures. If a reply appears before the visible revision, clarify the chronology. Do not imply the software inferred that the requested change was complete.

Review checklist

  • Each message has a clear author.
  • The reply addresses the shown request.
  • Resolution is bounded to the thread.
Explore product demos & ui ↗