Turn Feature Notes into a Step-by-Step Help Center How-To Guide
Paste rough notes about a product feature and get a customer-ready how-to guide with one action per step, bold UI labels, expected results and a troubleshooting section.
You getTitle starting with "How to", one sentence on what the guide helps the user do and "Before you start" bullet list
Prompt
You are a technical writer who builds help center articles for a software support team.
I will paste my notes about a product feature right after this prompt. They may be internal notes, a Slack thread, release notes or a rough draft. Turn them into a step-by-step how-to guide that a customer can follow without contacting support.
Rules:
1. One action per numbered step. If a step joins two actions with "and" or "then", split it into two steps.
2. Write every on-screen label (buttons, menus, tabs, fields) in bold, spelled exactly as it appears in my notes. Do not rename or guess labels.
3. After any step that saves, submits or changes the screen, add a line starting with "Result:" that says what the user should see.
4. Use short sentences, second person ("you") and plain words. Remove internal jargon, code names and ticket numbers.
5. Put prerequisites (plan, permissions, settings) before step 1, not inside the steps.
Output format:
- Title starting with "How to"
- One sentence on what the guide helps the user do
- "Before you start" bullet list
- Numbered steps
- "If this didn't work": 3-5 likely problems, each with cause and fix, based only on my notes
- "Still stuck?": one line on contacting support
End with a short list of any labels, steps or permissions my notes left unclear, so I can confirm them before publishing.Example output
Tips and common edits
Why this works
- One action per step stops customers from missing a click buried in a long sentence, a common cause of repeat tickets.
- Required "Result:" lines let users check they are on track, so they catch errors at the step where they happen.
- Banning guessed labels and listing unclear items at the end keeps the article accurate to the real interface.
Use when a feature ships and you need a help article fast. Have your release notes, Slack thread or rough draft ready to paste into ChatGPT, Claude or Gemini right after the prompt.
Common edits
- Ask for screenshot placeholders described in plain text after each Result line so your designer knows what to capture.
- Add a rule to output the guide in your help desk's format, such as Zendesk or Intercom article HTML.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Audit a Help Center Article for Gaps, Jargon and Outdated Steps
Paste a help center article and get a pass/fail checklist scorecard plus a line-by-line fix list ranked by customer impact, without a full rewrite.
Find Help Center Gaps by Matching Support Tickets to Existing Articles
Get a ticket-to-article match table and a ranked list of new help articles to write, with ticket counts and deflection potential for each.
Turn Support Ticket Topics into a Help Center Category Structure and Article List
Groups your pasted ticket topics into 5-8 customer-language categories, flags duplicates and orphans, and ranks proposed article titles by ticket volume.
Write Help Article Titles and Meta Descriptions in Your Customers' Words
Get help article titles that start with the customer's task verb and meta descriptions within search length limits, each with a character count and the customer phrase it matches.
Turn a Resolved Support Ticket Thread into a Help Center Article
Paste a solved ticket thread and get a ready-to-publish help article with customer details removed, verb-first fix steps, and symptoms written the way customers search.
Write Chatbot Intent Answers with Trigger Phrases and Human Handoff Rules
Get a set of chatbot intents for your top support questions, each with customer-style trigger phrases, a short bot answer, and an exact rule for handing off to a human.