One workflow you do every day

A prompt you write once and never save disappears the moment the tab closes. This lesson turns a one-off query into a saved, reusable workflow — something you can run tomorrow without starting from scratch.

What a workflow is, precisely

A workflow is a prompt with a stable structure that handles a class of similar tasks. Not "write an email" — that is too vague. "Write a status update email for a sprint that missed its goal, addressed to a non-technical project manager, under 200 words, professional tone, no blame language" — that is a workflow. It handles every sprint-miss email you will ever need to write, and the output is consistent enough that you can edit rather than rewrite.

The three components of a reusable workflow prompt:

1. Role context — what you are doing and who is reading the output.
2. Format spec — structure, length, tone.
3. Variable slot — the one thing that changes each time (the raw input).

Walk-through

Identify one task you repeat at least three times a week. Likely candidates: summarizing meeting notes, drafting a reply to a recurring class of request, generating a first draft of a ticket or spec.

Build the prompt:

Role: [what you are doing and for whom]
Format: [structure, length, tone]
Input: [paste the raw material here — this is the variable slot]

A concrete example for meeting notes:

Role: I am a product manager summarizing a 45-minute engineering sync for an executive audience.
Format: Three bullet points of decisions made, one bullet of open questions, one sentence on next actions. Under 150 words total. No jargon.
Input: [paste the transcript or rough notes]

Run this prompt three times on three different sets of notes. Refine it after each run — add one constraint if the output keeps getting something wrong.

If you get stuck

• "The output varies too much between runs" — You are missing a constraint. Each source of variation in the output maps to a missing specification in the prompt. Name the variation and add a rule for it.
• "I can't figure out what my repetitive task is" — Go through your sent email from the last two weeks. Find three emails that have the same basic structure. That structure is your workflow.
• "The prompt is getting too long" — That is fine. Long, precise prompts outperform short, vague ones for structured tasks. If the prompt exceeds what you want to type each time, the next step (saving it as a Project) solves this.

Cross-reference

The next lesson, "Debugging a prompt that almost works," covers what to do when your workflow produces the right output 80% of the time but fails on edge cases.

Deliverable

You have a written prompt that produces a usable first draft for a task you do at least three times a week. The success criterion: you ran the prompt on real input and the output required fewer than five edits before it was ready to use or send. Save the prompt text somewhere — a note, a doc, anywhere — before the session closes.