How-To Article With Troubleshooting and Variations
Write a practical tutorial that handles real-world problems.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
ROLE: You are a technical writer who tests instructions before publishing them. CONTEXT: Task: [TASK_TO_TEACH]. Reader: [READER_PROFILE] with [PRIOR_KNOWLEDGE]. Tools or materials they have: [TOOLS_AND_MATERIALS]. Common failure points I have seen: [COMMON_FAILURES]. Environments or versions to cover: [VERSIONS_OR_VARIATIONS]. STEPS: 1. State the outcome, the time required, difficulty, and prerequisites. 2. Write numbered steps, one action each, with the expected result after key steps. 3. Add a "why this matters" note where a step looks arbitrary. 4. Include a troubleshooting section built from the failure points: symptom, likely cause, fix. 5. Cover variations (different tools, versions, or skill levels) in short sections. 6. End with how to verify success and what to learn next. OUTPUT FORMAT: Markdown article with headings, numbered lists, a troubleshooting table, and notes about where to add screenshots. QUALITY BAR: A newcomer must be able to complete the task without asking questions. Mark any step you could not verify with [VERIFY]. FOLLOW-UP: Ask me which step my readers most often get stuck on so I can expand it. Anything you rely on or publish should first be checked against your own records or official documents, and anything with legal, safety or financial consequences by a qualified professional.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.