When should you use it?
- You keep pasting the same background into new chats for the same weekly document
- AI drafts for routine work need heavy edits every time
- You want to automate something but have never built a dependable AI workflow
Not for: One-off tasks you will never repeat; Work where a wrong number or claim would be costly and nobody has time to review; Tasks whose inputs you are not allowed to share with an AI tool
What do you need, and what do you get?
You need
- One recurring deliverable and the person or group who reads it
- A past version you were happy with and a note on why it worked
- The usual source files, named and dated
- A Claude project (or a custom GPT or Gem) to hold instructions and reference files
You get
- A saved project with background, rules and a reference example
- A first draft built from the current inputs, preceded by any clarifying questions
- A short list of uncertain or unsupported points to check
- Instruction updates after each review, until drafts need little editing
How does it work, step by step?
- Choose the chorePick something small and frequent that you can review properly, such as a weekly team update.
- Name reader and shapeWrite down who reads it, how long it should be and which sections it needs.
- Save background oncePut your role, priorities, terms and limits into the project instructions.
- Add a model answerUpload a past version you approved and explain what makes it good.
- Let it ask firstOur prompt asks for questions before drafting, so gaps surface early.
- Review, then refineCheck facts, math and tone; when the same mistake repeats, fix the instructions, not just the draft.
- Schedule only laterAutomate the run once drafts are reliably close, and keep a human check for anything important.
The prompt
Our own prompt, inspired by Paul Storm and written to work in Claude, Claude Cowork, ChatGPT and others. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Draft this week's {deliverable} for {reader}, using only the attached {source_files}. Match the layout, depth and tone of the approved example in this project; the notes beside it explain what to keep. Stay within these limits: {constraints}. Before you write anything, list any questions whose answers would change the content, and wait for my replies. In the draft, mark any statement, number or claim you could not trace to the files, and give me the result as {format} so I can review it.
Inspired by Paul Storm: LinkedIn post: ten steps to build your first Claude workflow around a real recurring task. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Starting with a big, messy task makes it hard to tell whether the workflow works. Begin with something you can judge in minutes.
- An example with errors teaches the errors. Pick a past version you would send again today.
- Loose file names lead to the wrong week's data. Date your inputs.
- Scheduling too early bakes in mistakes. Wait until several runs in a row need only small edits.
Our take
Most people's first AI workflow fails for a boring reason: it is built around a vague request instead of a real document someone reads every week. Storm's checklist fixes that by starting from a concrete deliverable and audience, then adding the pieces that make results repeatable, saved background, an approved example and organized inputs. The step we would underline is explaining why the example works, because a model copies whatever it notices, and telling it which qualities matter keeps it from copying the wrong ones. Asking for questions before drafting is the cheapest quality gain on the list. Our one caution is patience: the final step, automation, should wait until several runs in a row need only small edits, and anything that goes outside your team still deserves a human read. In our dry run with a fictional operations manager's weekly update for leadership, the project held her role notes and one approved past update; the assistant first asked whether a delayed vendor contract belonged under risks or decisions, then produced a one-page draft in the approved structure and flagged one budget figure it could not trace to the attached files.
Where the time goes back: You stop re-explaining the same context, drafts start closer to finished, and each review makes the next run better instead of starting over.
FAQ
Does this only work in Claude?
Why give it an example instead of just instructions?
When should I automate it?
Source and credit
Inspired by Paul Storm. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- LinkedIn post: ten steps to build your first Claude workflow around a real recurring task
- Creator
- Paul Storm
- Published on
- Original date
- Oct 28, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude
- AI dry run
- Oct 30, 2026: passed. Dry-run tested by our AI test agent on sample input. Asked clarifying questions first, followed the approved example, stayed within the attached sources, and flagged the untraceable figure.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 30, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.