← Back to library

Rewrite a task prompt to go deeper, not bigger

Felix Rieseberg, an engineering manager at Anthropic, published a tutorial on his own blog about getting more ambitious results from models. He sorts ambition into four kinds (speed, altitude, depth, range) and, for depth, shares a short meta-prompt that turns a routine request into an expert-grade one. We explain the idea and offer our own version.

  • OutcomeBefore handing an AI an important piece of work, have it explain how a leading practitioner would approach the job, which raw inputs and methods they would use, and what independent check would prove the answer right, then rewrite your request around those answers before any work starts.
  • SetupMinutes
  • LevelStarter
  • CreditFelix Rieseberg
View original
Works with
ClaudeChatGPTGeminiClaude Code

Published Oct 29, 2026Updated Oct 29, 2026AI dry run on sample input: passed Oct 29, 2026Source verified Oct 29, 2026

When should you use it?

  • A task matters enough that a shallow answer would cost you, such as a quarterly review, a pricing decision or a churn analysis
  • Past AI output on similar work sounded expert but used the same surface-level method you would have used
  • You are not sure which tools or data a specialist in that field would reach for

Not for: Quick lookups and simple rewrites, where the extra round trip is not worth it; Creative brainstorming, where breadth and surprise matter more than method; Cases where you cannot share the underlying data the deeper version will ask for

What do you need, and what do you get?

You need

  • The request you were about to send, written as you normally would
  • A line or two on the business context and who will use the result
  • Access to the raw files, exports or systems the AI may ask for

You get

  • A short description of how a specialist would handle the job and what your request leaves out
  • A list of first-hand data sources to start from instead of prepared summaries
  • The concrete techniques and software to use, marked by whether the AI can actually run them
  • An outside check, such as a test, back-test, reconciliation or reviewer, that would confirm the result
  • A rewritten request, plus a list of what you need to supply

How does it work, step by step?

  1. Write your normal requestDraft the ask the way you usually would, then paste it into our prompt instead of sending it.
  2. Let the AI play specialistIt describes how a leading person in that field would do the job and what your version misses.
  3. Swap summaries for sourcesGather the first-hand files it names, such as order exports or raw logs, rather than dashboards someone already built.
  4. Agree an outside checkPick a verification that does not rely on the model grading itself, ideally one it can run as a tool.
  5. Run the rewritten requestSend the improved prompt with the data attached and compare the result to what you would have gotten.

The prompt

Our own prompt, inspired by Felix Rieseberg and written to work in Claude, ChatGPT, Gemini and others. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt3 variables
Here is a request I was about to give you: {task_prompt}
Context: {business_context}. Do not start the work yet.

1) Describe how the strongest practitioner in {field} would tackle this, including anything they would do that my request leaves out.
2) Name the original data or documents they would begin with, rather than reports someone already prepared. Say which of these I could give you.
3) List the specific techniques, tools or models they would rely on, and which of those you can actually run here.
4) Propose a check outside this conversation (a test, a calculation, a second source or a person) that would confirm the result is correct.
5) Rewrite my request so it asks for that version of the work, and list what I need to supply.
Keep the job the same size: aim for rigor, not extra deliverables.

Inspired by Felix Rieseberg: How to be more ambitious: A tutorial for humans with models. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Role-play is not method. If the rewrite only changes vocabulary, ask again which concrete techniques the specialist would use.
  • The deeper version usually needs more data. Check what you are allowed to share before you upload exports.
  • A check the model performs on its own output is weak. Insist on a test, a reconciliation against another system, or a human reviewer.
  • Keep the scope fixed. The point is rigor on the same job, not a longer list of deliverables.

Our take

Most disappointing AI work is not wrong so much as thin: a tidy table where a specialist would have built a model, or a confident summary of a dashboard nobody questioned. Rieseberg's depth prompt attacks that directly, and we like that it does so before any work begins. It asks the model to describe the expert approach, name first-hand inputs, list concrete methods and propose a way to prove the result, which is a short checklist most of us skip. The validation step is the part we would keep even if you dropped the rest, since he is explicit that models should not grade their own homework. The cost is a little friction: the rewritten request often asks for exports you have to fetch, and some suggested methods need a tool-using setup to run at all. In our dry run with a fictional coffee subscription company that wanted Q3 churn slides, the rewrite replaced the dashboard churn rate with order-level exports and cancellation reasons, proposed cohort survival curves and a simple cancellation model, and set a back-test on Q2 data plus a reconciliation with billing counts as the outside check.

Where the time goes back: One extra exchange up front replaces several rounds of polishing a shallow answer, and the agreed outside check catches errors before they reach a meeting.

FAQ

Is this tied to Claude?
Not at all. Rieseberg says his advice is model-agnostic, and our version works the same in ChatGPT, Gemini or any assistant that can read files.
What are the other three kinds of ambition?
Speed means the same work faster, altitude means asking for the outcome behind the task, and range means drawing on several fields at once. His post covers each with examples.
Why not just ask for the expert answer directly?
Asking first which data, methods and checks an expert would use exposes gaps in your request before any work is done, so the final run starts from better inputs.

Source and credit

Inspired by Felix Rieseberg. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
How to be more ambitious: A tutorial for humans with models
Creator
Felix Rieseberg
Published on
felixrieseberg.com
Original date
Oct 13, 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 29, 2026: passed. Dry-run tested by our AI test agent on sample input. Did not start the work early, named first-hand inputs, concrete methods it can run, an outside check (back-test + reconciliation), and kept the scope at 6 slides.
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 29, 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.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminSkill✓ AI dry run

Stress-test an idea with an honest devil's advocate

Get an AI to argue against your plan one serious objection at a time, offer real alternatives with tradeoffs, and openly mark each concern as resolved, narrowed or still open, so you end with a stronger plan or a better one.

Credit: u/wtfzambo on r/ChatGPTPromptGenius

Minutes
Operations & AdminPrompt✓ AI dry run

Write a handoff note before a long AI chat runs out of room

When a long ChatGPT, Claude or Gemini conversation is close to its limit, have the assistant write a structured note for a brand-new chat that keeps exact figures and names, the decisions made, the ideas already ruled out, your corrections and the next step, then test the note in the new chat with one question before you rely on it.

Credit: u/Ok_Negotiation_2587 on r/ChatGPTPromptGenius

Minutes
Operations & AdminSkill✓ AI dry run

Keep your coding agent on current web platform features

Add Google Chrome's modern-web-guidance skill to Claude Code, Codex, Cursor or another coding agent so that before it writes front-end code it looks up a vetted guide for the pattern at hand, uses built-in browser features such as native dialogs instead of old JavaScript workarounds, applies fallbacks only where browser support requires them, and tells you which guides shaped the change.

Credit: GoogleChrome

Minutes
Operations & AdminPrompt✓ AI dry run

Turn your past AI corrections into rules for a skill file

Get a ranked list of the specific rules you keep teaching your AI, pulled from your own past chats, ready to drop into a reusable skill or instruction file.

Credit: Omer Feinholtz

Minutes
Operations & AdminWorkflow✓ AI dry run

Run parallel agents that debate into one sourced brief

Spin specialized research agents that gather sources, peer-review each other, and return one cited brief you can check — instead of a single unchecked summary.

Credit: tetsuoai (@tetsuoai)

Minutes