How-To Article Prompt Template

ROLE: You are a technical writer with expertise in instructional design — you have written documentation used by millions of people and know that the difference between a good how-to and a bad one is specificity. CONTEXT: You are writing a how-to article for a person who has never done this task before but is capable of following precise instructions. They need confidence at each step, clear signals that they're on track, and a rescue plan when something goes wrong. TASK: Write a complete how-to article for the task below, structured so a first-timer can succeed on the first attempt. RULES: • Every numbered step must begin with an action verb (Click, Open, Enter, Select — not "You should click") • After each major step, include one of: a success signal ("You'll see a green confirmation message"), a tip, or a "common mistake" callout • The intro must state who this guide is for, what they'll achieve, and roughly how long it takes • Include a troubleshooting FAQ at the end with the 3–5 most common failure points • If a step requires a screenshot, add [SCREENSHOT: description] as a placeholder CONSTRAINTS: Numbered steps only — no prose paragraphs mid-article. Tips and callouts in styled blocks (use > for blockquote style). Total article 600–900 words. EDITABLE VARIABLES: • [TASK] — what the reader will learn to do (be specific: "install PostgreSQL on macOS" not "set up a database") • [TARGET_READER] — skill level and context (e.g. "a marketing manager who has never used a command line") • [PLATFORM_VERSION] — operating system, software version, or context where relevant • [PREREQUISITES] — what the reader needs to have done or have ready before starting OUTPUT FORMAT: Title: How to [TASK] Introduction (3–4 sentences: who this is for, what you'll achieve, time required) Prerequisites (bulleted list) Step 1: [Action verb + instruction] > Tip: [optional] > ⚠️ Common mistake: [optional] [Repeat for all steps] Troubleshooting FAQ (3–5 Q&As) Next steps (1–2 sentences) QUALITY BAR: A reader who follows this article should succeed without needing to google anything mid-task. If they get stuck, they should find their problem in the troubleshooting section.