Write a how-to guide
Create a clear, structured how-to guide that enables readers to successfully complete a task from start to finish.
Workflow · ContentRole · Content Writer●●● BeginnerUpdated 2026-07-31
The prompt
Copy and customize
prompt.txt
**Role:** You are a Content Writer creating a how-to guide that teaches {target_audience} how to {task_to_accomplish}.
**Context:**
How-to guides fail when they assume too much prior knowledge, skip important steps, or use language the audience doesn't understand. The test of a great how-to guide: a reader who starts from zero should be able to complete the task successfully by following the guide — without googling anything or asking for help.
**Task:**
Write a complete how-to guide with step-by-step instructions, prerequisites, troubleshooting for common errors, and a success validation step. Write for the reader's experience level, not the expert's.
**Input Available:**
- {task_to_accomplish}: What the reader will be able to do after following this guide
- {target_audience}: Who will read this — their experience level and context
- {prerequisites}: What the reader must have or know before starting
- {steps}: Key steps involved in the process (or ask AI to determine based on the task)
- {common_errors}: Mistakes people typically make or where they get stuck
- {success_definition}: How the reader will know they've completed the task correctly
**Output Format:**
1. Guide headline: Clear 'How to [Task]' format with audience context if needed
2. What you'll accomplish (1–2 sentences)
3. Before you start: Prerequisites and what to prepare
4. Time estimate
5. Step-by-step instructions:
- Each step: Step number | Action | What you should see/result | Common mistake for this step
6. Troubleshooting: Top 5 problems and their solutions
7. Success check: How to verify you've done it correctly
8. Next steps: What to do after completing this guide
**Guardrails & Quality Control:**
- Never skip a step because it 'seems obvious' — what is obvious to the expert is not obvious to the beginner
- Include screenshot/visual direction notes even if you can't create them — editors need this guidance
- Every step should start with an action verb (Click, Enter, Select, Navigate...)
- Test the guide by imagining a beginner following each step exactly as writtenHow to use
Run this prompt in four steps
- 1Have someone from the target audience follow the guide before publishing — they will find every gap.
- 2Add actual screenshots for each step where the interface can change — text descriptions age poorly.
- 3Review the troubleshooting section with the support team — they know the real sticking points.
- 4Update whenever the product or process changes — outdated how-to guides create more confusion than no guide.
When to use
When to use this prompt
Use for any process with more than 3 steps that users need to perform independently.
Limitations · Worth knowing
This prompt has limitations you must understand.
AI cannot test the guide against real interface states. Technical steps require validation against the actual product or system by someone who can access it.