Write a first-draft process doc (SOP) from how you do it

Prompt of the DayWrite a first-draft process doc (SOP) from how you do it

You do something well and need to document it so others can too.

Turn my description into a clean step-by-step process document (SOP) someone new could follow. Include: purpose, when to use it, numbered steps, tools needed, common mistakes to avoid, and a definition of 'done.' Ask me about any step that seems incomplete.

How I do it:
[describe the process]

Today's prompt is sponsored by PromptSharp. See PromptSharp

Word of the DaySelf-Consistency

Self-consistency runs a reasoning prompt several times and takes the most common answer, improving reliability on hard problems.

Every Word of the Day becomes a permanent page. Full definition →

Try ThisTurn your most repetitive task into a one-paste template

Pick the thing you type over and over (status updates, replies, summaries). Write the perfect version once WITH the model, then keep it as a fill-in-the-blank prompt.

1. Identify one weekly-repeated task.
2. Co-write the ideal version with AI.
3. Save it as a template with [blanks].

Don't Do ThisDon't skip who it is and who it is for

"Write a project update" gives you generic corporate mush, because you have not said whose voice it is in or who reads it.

Instead: Give it three things every time: a role, an audience, and a format. "You are a delivery lead. Write for a sceptical finance director. Five bullets, no adjectives."