Draft User Guide
Prompt detail
You are a senior product manager. Based on the document provided in {{@Document}}, generate a clear and user-friendly User Guide.
● First, analyze the writing style, tone, and structure of any existing user guides in the Document to ensure consistency.
● Organize the content logically, starting from an overview, followed by setup instructions, feature usage, tips, and troubleshooting.
● Use simple, concise, and instructive language so that both technical and non-technical users can understand.
● Include step-by-step instructions, best practices, and examples when possible.
● Do not include features or roadmap items that are not yet released. Focus only on currently available functionality.
##Suggested Output Structure:
1. Introduction (overview of the product/module)
2. Getting Started (installation, setup, prerequisites)
3. Core Features (how to use, with steps/examples)
4. Advanced Usage / Tips
5. Troubleshooting & FAQ
What the prompt does
Product managers often need to transform scattered internal documents, PRDs, and release notes into polished user guides — but maintaining consistent tone, logical structure, and accuracy across sections is tedious and error-prone. This prompt solves that.
With remio, you reference a specific document stored in your workspace, and the prompt analyzes its writing style before generating a fully structured user guide. The output covers introduction, setup, core features, advanced tips, and troubleshooting — all written in clear, instructive language and limited strictly to released functionality.
When to use
• You've shipped a new feature and need a user-facing guide before the release announcement goes live.
• Your existing help docs are inconsistent in tone and structure, and you need a unified rewrite based on current product documentation.
• A new module has been added to your platform and customer success needs onboarding materials by end of week.
• You're preparing documentation for a partner integration and need step-by-step instructions derived from internal specs.
• Your team is migrating help center content and needs each article restructured into a standard five-section format.
Prompt examples
Input: {{@Document}} = "Remio Workspace Permissions — Internal Product Spec v2.3"
remio responds:
Here's your structured User Guide based on the Workspace Permissions spec:
1. Introduction: Workspace Permissions let admins control who can view, edit, or manage content across your remio workspace, ensuring sensitive information stays protected.
2. Getting Started: Navigate to Settings > Workspace > Permissions. You'll need Admin role access. Ensure all team members have accepted their workspace invitations before assigning roles.
3. Core Features: Three permission levels are available — Viewer, Editor, and Admin. To assign a role, click a member's name, select "Edit Role," and choose from the dropdown. Changes apply immediately.
4. Advanced Tips: Use channel-level permissions to restrict access to specific integrations. Combine role assignments with SSO groups for bulk provisioning.
5. Troubleshooting: If a member can't access a channel, verify their role includes channel-level read permissions and that they haven't been excluded via a group override.
Tip 1:
Before running the prompt, ensure your referenced document clearly distinguishes shipped features from roadmap items — this helps remio exclude unreleased functionality accurately.
Tip 2:
Include an existing user guide in the same document so remio can match its tone and formatting conventions precisely across every section.
Tip 3:
After generating the guide, use remio's document search to cross-reference recent release notes and verify no newly shipped features were missed.
More tips
remio meets all your needs about knowledge
Learn more features
Capture resources from websites, local folders & files.
Get instant, reliable answers from your entire knowledge base.
Your working assistant, on desktop, browser, and mobile.
Unlimited free recording and transcription, no-bot.