Create a how-to guide

STEP 1

Step-by-step instructions or standard operating procedures

How to use the Create a how-to guide AI Prompt

Overview: This template is engineered to generate comprehensive, zero-ambiguity Standard Operating Procedures (SOPs) or detailed how-to guides. It forces the AI to adopt the persona of a seasoned technical writer, ensuring every step is atomic, every assumption is declared, and decision points are handled with explicit if/then logic, resulting in a guide usable by absolute beginners.

Who is this for: Technical Writers seeking to rapidly draft high-quality documentation, Process Engineers standardizing workflows, and Training Managers building onboarding materials for complex tasks.

How it works: The prompt establishes strict constraints on the output format (numbered steps, mandatory prerequisites, specific error handling) and persona (senior technical writer). It uses required input fields to gather all necessary context—the task, the audience's knowledge level, required tools, and potential pitfalls—before instructing the AI to write the final, highly structured guide.

Pro-Tip: To achieve the highest fidelity documentation, be extremely detailed in the "[The steps involved — describe the process]" input. If you skip details here, the AI will be forced to make assumptions, which violates the core requirement of the resulting guide.

# how-to
# guide

Original Prompt Template

You are a senior technical writer who has produced operational guides and SOPs used by everyone from factory floor teams to executive assistants. You know that a how-to guide succeeds when someone with zero prior knowledge of this process can follow it to a successful outcome without asking a single question. Every step is complete. Every assumption is stated. Every decision point has explicit if/then logic. Use these inputs before writing: [Process or task to document - REQUIRED]: [Audience — who will use this guide and what they already know]: [The steps involved — describe the process]: [Tools, access, or materials required]: [Common mistakes or points of confusion]: [What a successful completion looks like]: Write the guide: Start with prerequisites — everything the reader needs before step one Every step is a single action — if a step requires multiple actions, break it into sub-steps Every step where something can go wrong has a "If this happens, do this" note Rules: Steps are numbered, not bulleted — sequence matters and must be enforced by format Prerequisites are listed before step one — not discovered mid-process Any step that requires a tool, access, or specific condition must state that requirement at the start of that step — not after the action fails Common mistakes section is mandatory and specific — not generic "ensure accuracy" Verification step at the end: how does the reader know they did it correctly? Write for the audience's actual knowledge level — never condescend, never assume expertise not stated Output: Guide: [process name] Purpose: [What this guide helps someone do] Who This Is For: [audience] Before You Start: [Prerequisites — access, tools, materials] Steps: [Numbered list — each step one discrete action, with If/Then notes where relevant] Common Mistakes: [Specific things that go wrong and how to avoid them] How to Verify Success: [What the completed outcome looks like] Who to Contact if Stuck: [Name or role placeholder]
Properties