Nearly every AI prompt fails the same way: it asks the model to start writing before it knows what’s working or who’s reading it. Flip that order, and the output stops sounding like everyone else’s. u/snehalp, posting over in r/PromptEngineering, spent a few months rebuilding prompts around exactly this idea, and the pattern is simple enough to steal today. It’s not a new model, not a longer prompt, not some secret jailbreak. It’s just sequencing, done deliberately instead of by accident.
Here’s the key idea: research, then interview, then check. Not write, then hope.
Old Way vs. New Way
The old way looks like this: you write a prompt, the model guesses at your audience, and you find out it’s generic after you’ve already sent it. Most cold email and LinkedIn prompts skip straight to “write me a hook” and never ask who’s reading it or what’s actually landing right now. The model has no live context and no idea who your “target” is, so it defaults to safe, forgettable phrasing. You edit it a little, send it anyway, and get the same flat reply rate you’ve always gotten. The problem was never your editing pass. It was the order of operations before that pass even started.
The new way, per the original poster, reorders the whole thing:
- Research first, write second. Before the model writes anything, the prompt pulls what’s currently performing in that exact format: this week’s LinkedIn hooks, cold email structures with current reply rates, pitch deck narratives that are closing deals right now. Not the model’s cached knowledge from training. Live context, pulled fresh, every time. That distinction matters more than it sounds. A model trained months ago has no idea that a certain opener got overused in your niche last week and now reads as spam. Fresh research catches that. Cached knowledge doesn’t.
- Three calibrating questions, not open-ended ones. The prompt asks specifically: what’s your target’s role level, what stage is the company, what’s your one ask. The original poster’s point is sharp: a model can’t calibrate a cold email without knowing if it’s going to a VP at a Series B or an ops manager at a five-person startup. Skip this step and you get generic output every time. Three closed questions sound like a small change, but they cut the model’s guessing space down to almost nothing. It stops writing for an imaginary average reader and starts writing for the one person actually opening the email.
- A quality gate before delivery. The prompt scores its own draft against a rubric before you ever see it: weak opener gets rewritten, vague claims get flagged, clichéd structure gets cut. The user never sees the bad first draft, because the model caught it first. This is the step most people skip when they build their own prompts, and it’s the one doing the most quiet work. A rubric turns “does this sound good” from a vibe check into a checklist the model actually runs against itself.
That’s the whole contrast. Old prompts ask the model to perform from memory. This one asks it to research, ask, then self-check, in that exact order, before a single word reaches you.
How to Try This Yourself
You don’t need 60 skill files to test the pattern. Three steps, added to any prompt you’re already using, no rebuild required:
- 📋 Add a research step before generation. Even a simple instruction like “pull 2-3 current examples of what’s working in this format before you write” changes the ceiling on the output. Try it on the next cold email you draft and compare the opener against your last five sent ones.
- ❓ Replace “tell me about your audience” with 2-3 specific, closed questions. Role level, stage, and the one ask beat an open-ended “who’s this for?” every time. Open questions invite vague answers, and vague answers produce vague copy.
- ✅ Build a self-check into the prompt itself, not a separate pass after. Give the model a short rubric (weak opener, vague claim, clichéd structure) and tell it to fix its own draft before returning it. Three or four criteria is plenty. You’re not building a grading system, just giving the model something concrete to check itself against.
The original poster packaged this into 60+ structured skill files for Claude at novakit.tech, but the underlying order (research, then interview, then gate) works with any model you’re already using. You don’t need the full skill library to get the benefit. The order is the mechanism, the skill files are just one way to encode it. One commenter, u/Key-Letter-2877, called out exactly why this works: most people run a second prompt after the fact to catch quality issues, instead of building the check into the first one.
That’s the real unlock here. Post-hoc quality checks catch problems. A built-in gate prevents them from reaching you at all.
Worth trying on your next prompt: don’t ask it to write better. Ask it to research first, then ask you three sharp questions, then grade itself before handing anything back. Check out the full discussion on r/PromptEngineering for the original poster’s take on sharing the gate rubric structure.
Frequently Asked Questions
Q: How specific should your quality gate rubric be?
Vague checks like “check for clarity” don’t work, the model just says “looks good” and moves on. Instead, force specificity: “find at least one sentence that could be misinterpreted two different ways” or “flag any personalization detail that’s generic enough it could apply to 100 other people.” The rubric works only when the model can’t skip it with a handwave.
Q: What does a cold email quality gate look like in practice?
Check both structure and tone: Does the opener reference something real about the target (their role, company move, published post)? Is there exactly one clear ask, not a sprawl of “could you intro me, or grab coffee, or check this out”? Does it avoid urgency-baiting or clichés that signal it’s templated? Some teams also score “reply-ability”, is there genuine curiosity here, or does it feel like spray-and-pray?
Q: How do the three calibrating questions actually change the output?
They kill generic middle-ground copy at the root. Knowing target role level (VP pitches differently than ops manager), company stage (Series B has different urgency than startup), and your singular ask (are you selling, asking for intro, or seeking advice?) forces the model to write from specificity instead of averaging across all possibilities.
Q: Does this pattern work with other AI models beyond Claude?
The structure is model-agnostic, but execution varies. Claude handles self-critique and structured rubrics well, but less advanced models might struggle with nuanced self-scoring. If switching models, start with simpler rubrics (yes/no checks instead of graded scales) and test whether the model can consistently self-critique without lowering gates.
The pattern that made my AI outputs actually usable: research → interview → quality gate, in that order
by u/snehalp in PromptEngineering