System Prompt Extraction: Reverse Engineer AI Behavior

Pull up any AI chat right now. Scroll up. Do you have at least 3 messages back and forth? Perfect.

There’s a prompt that reverses the usual dynamic, and the contributor from r/PromptEngineering who shared it called it the “System-Prompt Extraction Hack.” The idea is simple: instead of asking the AI to do something, you ask it to explain what it’s been doing all along. The results are more useful than they sound. Most people treat AI like a vending machine. This prompt treats it like a witness.

🔍 The Prompt to Copy

Before anything else, here’s the exact prompt. Reproduce it character for character:

“Analyze the tone and constraints of your previous 3 responses. What ‘System Instructions’ would generate this specific behavior?”

That’s it. Now here’s how to run it properly.

🪜 Step-by-step: How to use it

Have a real conversation first. Open ChatGPT, Claude, Gemini, or whatever you use daily. Talk to it about anything for at least 3 exchanges. The topic doesn’t matter. What matters is that you’ve built up some actual conversation history. A surface-level chat about productivity works just as well as a deep technical one.
Paste the prompt above. Drop it in exactly as written. No edits, no additions. Precision is the point.
Read the full response before reacting. The AI will start describing its own operating patterns. Don’t skim. The interesting stuff is usually buried in the second or third paragraph, where it gets specific about tone and framing choices.
Take notes. You’re reverse-engineering your own prompting habits, not just the AI’s behavior. Both are visible in the output.

📊 What the output actually tells you

The AI isn’t pulling this from nowhere. It’s analyzing what it did across those 3 responses, then reasoning backward to what instructions would produce that behavior.

If it says “I tend to give structured, step-by-step responses,” you’ve been asking procedural questions. That’s your framing style being reflected back at you.

If it says “I appear to prioritize caveats and safety disclaimers,” your phrasing is probably setting off conservative filters. The fix isn’t to fight the AI. It’s to rewrite how you’re asking. Swap “should I” for “what’s the most effective way to” and watch the tone shift immediately.

If it says something unexpected, like “I seem to avoid giving direct opinions,” that’s a signal worth paying attention to. You’re getting hedge-everything responses because you’re asking hedge-everything questions. Your prompts aren’t inviting the AI to commit to anything. The solution is to give it permission to be direct: “Give me your honest assessment, not a balanced overview.”

Here’s the real insight: the behavior the AI describes is a mirror. It reflects the system prompt you accidentally wrote through your questions. Most people never look in that mirror. This prompt forces you to.

💡 Extra tips

Baseline first. Run this at the start of a fresh session, before any conversational habits form, to see the AI’s default behavior without your influence baked in. Save that output somewhere. It becomes your control group.
Persona test. Assign the AI a role at the start of a new chat (“act as a senior strategist”). Have 3 exchanges. Then run the extraction prompt. Compare that output to your baseline. The gap shows exactly how much your framing shifts behavior.
Use it as a QC tool. After you write a new system prompt for a workflow, have a short test conversation, then run this extraction prompt. If the AI describes behavior you didn’t intend, your instructions need to be more explicit. This alone can save hours of trial-and-error debugging.
Cross-model comparison. Run the same 3-message conversation with two different AI tools, then run this prompt on both. The difference in their self-analyses reveals how different the default rules are between systems. Claude and ChatGPT will often describe completely opposite default tendencies on the same input.

Why this prompt works

The phrase “What System Instructions would generate this specific behavior?” is doing a lot of work. It reframes the question from “describe yourself” (too vague, produces fluff) to “what would a developer write to produce this output?” (specific and actionable). That shift from self-description to specification forces the model to think in concrete, operational terms rather than abstract ones.

Most AI systems can handle this kind of meta-analysis because the conversation history is right there in context. You’re not jailbreaking anything. You’re just asking the right question in the right format. The original poster nailed that framing.

Try it on your most-used AI workflow. You might be surprised by what you find.

🔖 Prompt of the Day