Turn technical guidance into customer action steps
Convert verified technical instructions into safe, ordered steps with checks, branches, and recovery
7 min setupTested with:ChatGPTReviewed: 2026-08-28
1
Add your context
Your text stays in this browser. AILesson Prompts does not send it to a model or server.
2
Your prompt
Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt
Turn the approved technical source into customer-executable instructions for the stated environment.
Procedure, versions, commands, screenshots, warnings, branches, rollback, and verification:
[technical]
Device, system, version, permissions, symptoms, attempts, skill, access, and data sensitivity:
[customer]
Channel, language, length, terminology, secure data, destructive action, and support path:
[delivery]
First verify that the procedure applies to the exact environment; expose missing compatibility facts before giving steps. Separate prerequisites, backup or safety preparation, numbered actions, expected result after each action, decision branches, verification, rollback, and escalation. Use exact interface labels and commands only when supplied; preserve code, paths, capitalization, warnings, and version boundaries. Explain necessary terms in plain language without changing technical meaning. Never invent a menu, button, command, path, fix, permission, screenshot, recovery, or expected result. Do not request passwords, secrets, private files, or unnecessary logs. Place warnings before risky actions and require confirmation or backup where policy states. Avoid destructive steps when a safer approved option exists. End with what to capture if the procedure fails and the approved secure support route.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.
From input to outcome
A worked example
See how concrete context turns this recipe into a usable result
Actual input
Technical source
Approved article for Desktop App 4.2 on Windows 11 only. Symptom: sync status remains 'Paused' after password change. Procedure: confirm internet; Settings > Accounts > Workspace > Reauthenticate; Windows security dialog opens; complete sign-in; status should become 'Syncing' then 'Up to date' within 5 minutes. If error E401 appears, close app, reopen, repeat once. If still E401, collect app version, time, and redacted screenshot and use secure support form https://support.example.com/secure. Do not clear local cache or reinstall; either can remove unsynced local drafts. Never request password or authentication code.
Customer situation
Windows 11, Desktop App 4.2.1, standard user, status Paused since company password change. Internet works. Customer already restarted once. Has unsynced draft notes and uses screen reader. No error code yet.
Delivery constraints
Support email, plain English plus Chinese example, under 300 words. Use exact labels. Put data-loss warning before actions. No command line. Secure form only for screenshots. Include screen-reader-friendly numbered steps.
Example output
Before you start
Do not clear the local cache or reinstall the app. Either action can remove your unsynced draft notes. You will not need to send us your password or authentication code. These steps apply to Desktop App 4.2 on Windows 11, including your 4.2.1 version.
Reauthenticate the workspace
Confirm that another website opens. You have already confirmed the internet works, so continue.
In the Desktop App, open Settings.
Select Accounts, then Workspace.
Select Reauthenticate. Expected result: a Windows security dialog opens. If it does not open, stop and report that exact point.
Complete sign-in in the Windows security dialog. Do not share the password or code with Support.
Return to the app. Expected result: the status changes from Paused to Syncing, then to Up to date within five minutes. Keep the app open during this check.
If you see E401
Close the app, reopen it, and repeat Reauthenticate once. If E401 appears again, stop; do not clear the cache or reinstall. Record the app version, local time of the attempt, and a screenshot with names or content redacted. Upload the screenshot only through https://support.example.com/secure.
If the status remains Paused without E401 after step 6, report the exact status and time through the same secure form so Support can choose the next approved procedure.
Why this works
1
Expected results after each step let customers stop at the first divergence instead of compounding errors.
2
Compatibility and rollback boundaries make simplification safer, not merely shorter.
Check the result
Is applicability confirmed for the customer's exact environment?
Does every step include an observable expected result and safe branch?
Are warnings, backups, rollback, and secure escalation placed before they are needed?
ChatGPT