Turn a Messy Paragraph into a Clear Numbered Step-by-Step Guide

Paste any rambling instructions and get a numbered how-to guide with one verb-led action per step, a prerequisites list, and flagged gaps instead of guesses.

You getTitle, prerequisites and steps

Prompt

Prompt
Act as a technical writer who turns messy instructions into clear how-to guides.

I will paste a paragraph, post or set of notes right after this message. Rewrite it as a numbered step-by-step guide someone can follow without rereading the original.

Rules:
1. Every step starts with a verb and contains exactly one action. Split any step that joins two actions with "and" or "then".
2. Keep the original order unless it is clearly wrong. If you reorder, explain why under Notes.
3. Do not invent steps, settings, values, menu names or tools. If something is missing or vague, write "Gap:" inside the step with a short note on what is unclear.
4. Put everything the reader needs before starting (accounts, tools, files, permissions, skills) under Prerequisites, not inside the steps.
5. Keep each step under 25 words. Add a short "Check:" line after a step only when the reader needs to confirm it worked.

Output format:
- Title: one line starting with "How to"
- Prerequisites: bulleted list
- Steps: numbered list
- Gaps to fill: numbered list of every flagged gap, each with the question to ask the original author
- Notes: any reordering or assumptions

If the pasted text is too thin to make a usable guide, say so and list what is missing before writing anything.

Example output

At a glanceWhat the guide produced from one Slack postTravel expense submission in Ledgerly
Numbered steps
12 steps
One verb-led action each
Prerequisites listed
4
Account, receipts, manager, project code
Gaps flagged
4 questions
Instead of guesses
Notes on changes
3
Moves, splits and assumptions

Example for: a team lead's Slack post explaining how to submit a travel expense in the company's finance portal, Ledgerly.

How to Submit a Travel Expense in Ledgerly

Prerequisites
  • A Ledgerly account with the Employee role
  • Photos or PDFs of every receipt
  • Your manager's name as listed in Ledgerly
  • The project code for the trip
Steps
  1. Log in to Ledgerly.
  2. Click New Expense on the dashboard.
  3. Select Travel as the expense type.
  4. Enter the trip start and end dates.
  5. Type the project code in the Project field.

    • Gap: the post says "use the usual code" but does not say where to find it.
  6. Upload one receipt per line item.

    • Check: each line shows a green paperclip icon.
  7. Enter the amount for each receipt in the original currency.
  8. Choose the currency from the dropdown.

    • Gap: unclear whether Ledgerly converts automatically or the employee must enter the converted amount.
  9. Add a one-line purpose for the trip in the Description field.
  10. Select your manager as the approver.
  11. Click Submit.

    • Check: the status changes to "Pending approval."
  12. Wait for approval before booking reimbursement.

    • Gap: the post mentions "a few days" but gives no deadline or follow-up contact.
Gaps to fill
  1. Where does an employee find the project code for a trip?
  2. Should foreign-currency amounts be entered as-is or converted first? If converted, which rate?
  3. How long does approval usually take, and who should the employee contact if it stalls?
  4. Is there a submission deadline after the trip ends? The post says "don't wait too long" without a number.
Notes
  • Moved "make sure you have all your receipts" from the end of the original post into Prerequisites, since the reader needs them before step 6.
  • Split the original "add the dates and project and upload receipts" into steps 4, 5 and 6.
  • Assumed the Description field is required because the post says "always explain the trip"; confirm with the author.
Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • One verb and one action per step stops bundled instructions that readers skip or misread.
  • Flagging gaps instead of guessing keeps the guide accurate and gives you exact questions for the author.
  • Separating prerequisites from steps means readers gather what they need before starting, not halfway through.

Use when you have a Slack message, forum post, email or meeting note explaining a process. Paste the prompt into ChatGPT, Claude or Gemini, then paste the original text right after it.

Common edits

  • Ask for a shorter version with no Check lines for a quick internal wiki entry.
  • Specify the reader, such as a first-week new hire, so the model adds more context to each step.

Prompt details

By
Prompts-GPT editors
Published
How prompts are written and checked

Did this prompt work?

Keep exploring

More in Writing