Opus 4.7 and OpenAI 5.5 Made Your Prompting Style Obsolete

Nate B Jones ยท ~25 min ยท Deep-Dive Analysis
Video Thumbnail

๐Ÿ”‘ Key Takeaways

  • Prompt engineering is table stakes โ€” necessary but no longer a differentiator. The new skill is asking great questions.
  • Agents are now ~100x more powerful than 6โ€“8 months ago (better tool use, longer sessions, larger context).
  • Mental model shift: AI = senior partner, not junior assistant.
  • Three principles of the AI Question Method:
    1. Flashlight Intent โ€” convey the center of your focus AND the edges.
    2. Multi-Directional Synthesis โ€” ask questions that force AI to synthesize across complex dimensions.
    3. Data + Opinion Breadth โ€” ensure AI engages with ALL data sources and knows your thesis across them.
  • You can prime AI memory to remind you when you fall back into flat, directive prompting.

00:00 Prompt Engineering Is Dead โ€” Long Live It

Nate opens provocatively: "Prompt engineering is a 2025 conversation." He acknowledges the eye-roll โ€” people feel prompting is passรฉ because "you can just ask AI and it works." But his point is nuanced: prompt engineering skills are now baseline requirements. You don't get credit for them anymore.

"Yes, absolutely true. It's table stakes now. It is table stakes now. You got to be good at it. You don't get credit. Sorry. Welcome to the way AI moves."

He notes that even people at AI labs say "just ask for what you want" โ€” but this only works when people actually know what they want. For complex agentic knowledge work, most people don't.

01:00 The 100x Agent Leap: What Changed with 4.7 & 5.5

Claude Opus 4.7 and OpenAI o5.5 (released in the prior ~2 months) represent a qualitative shift:

  • Better tool calling and data retrieval
  • Ability to work for much longer periods
  • Dramatically expanded scope of corporate impact

Nate frames this as a 100x improvement in agent power โ€” but our prompting style has NOT evolved 100x. That gap is the core problem.

07:12 He notes a "second acceleration" since these launches, particularly with o5.5 in Codex, making the question-based approach more viable than ever.

02:33 The AI Question Method โ€” A New Mental Model

Nate introduces the "AI Question Method":

โŒ Old: Prompting

You ask โ†’ you get an answer. Transactional. Task-based. You define every detail.

โœ… New: Questioning

Partnership, exploration, co-thinking. You form questions that enable the agent to do its best work.

"We are really in a question world, not a prompt world."

03:03 Senior Partner vs. Junior Partner

THE biggest mental model shift for 2026:

2025: Junior Partner

Be very specific, careful, prescriptive. Define every step.

2026: Senior Partner

Share context, ask questions, trust its judgment, let it push back.

When you treat AI as a senior partner, you unlock its full capabilities. When you micro-manage it like a junior, you constrain it.

03:38 The Good Manager Story

From Nate's time on a marketing team at Amazon, his manager would:

  1. Share the problem space openly: "I need you to dig into this"
  2. Provide raw materials: CSVs, Excels, context
  3. State the goal: marketing attribution โ†’ deck + doc for leadership
  4. Set quality standards: "clear, incisive, tells a real story"
  5. Leave room for autonomy: "I'm going to leave a lot to you"
  6. Guide with questions along the way

04:41 That same management approach now looks exactly like a good agentic prompt in 2026.

05:17 Defining "Agents" for This Context

โœ… This Video

Heavy knowledge work in Claude Code, Co-Work, Codex. Deep partnership thinking with frontier models. Unique, custom, creative problem-solving.

โŒ Not This Video

Agentic pipelines (customer service tickets, invoice processing). Defined, predictable workflows. Need evals & structured testing.

09:09 Principle #1: The Flashlight โ€” Intent with Edges

Your questions need a "center of the flashlight" and visible edges.

๐Ÿ”ฆ Center = Your thesis / perspective / angle

โŒ No Perspective

"Help me learn more about the Mona Lisa"

โœ… Clear Thesis

"I have a thesis that painting the Mona Lisa shaped Da Vinci's relationships late in life. Investigate from that angle."

๐Ÿ”ฒ Edges = Boundaries & exclusions

11:18 Example: Meeting notes โ†’ report, but 15 min was about an unrelated project. Explicitly: "Excise that. Do not include the greenlighting discussion."

Common Mistakes

  • Overly open-ended questions (no center)
  • Overly closed questions (no room to explore)
  • Missing edges (AI wanders into irrelevant territory)

12:51 Principle #2: Invite the AI to Synthesize Across Complex Questions

Ask the AI to consider what "good" looks like in a more open-ended way than writing an eval. Evals are great for pipelines โ€” but for creative knowledge work, you need the AI to explore quality.

Worked Example โ€” PR/FAQ Document

14:06 Fictional scenario: Prime Video launching 3D holographic soccer players for the World Cup.

  • Question 1: "How is this accessible whether someone has had a 3D experience before or not? How do we convey that in the press release?"
  • Question 2: "Think about the interrelationship between software and hardware โ€” convey emotion in the press release AND list technical seamlessness in internal FAQs."
"I did not say THIS is how I want it woven together... I asked the AI to wrestle with me on it and think it through and come back."

15:58 "I'm not seeing people doing it. I'm not seeing people actually say, let me ask multiple open-ended questions and let the AI synthesize across."

17:22 Principle #3: Data Breadth + Your Opinions

Ensure the AI engages with ALL your data sources while knowing your opinions across them.

The Working Context Folder

17:51 Nate's Codex workflow: have the AI organize files into a single working context folder:

  • Formal files: docs, PowerPoints, Excel, code
  • Informal files: meeting transcripts, notes

The Problem

18:18 People assume AI will uniformly dig into all files. It often doesn't โ€” your question inadvertently angles it toward one file and it dives deep there while ignoring others.

The Fix

Ask questions that explicitly reference the breadth of data and convey your opinions across that breadth, so the AI has reason to engage with every source.

19:57 Worked Example: MRR Product-Led Growth Analysis

A full example combining all three principles.

Setup

  • Goal: Increase MRR (Monthly Recurring Revenue)
  • Data: Voice of customer transcripts, support tickets, PRDs, launch announcements, analytics
  • All organized into one folder

The Question

"My thought is that our product-led growth angle from the last two years is broken. I don't think we're getting good margin. I think that shows up in flatter MRR growth over the last 6 months, in dead-cat-bounce launches, and in our own thinking in the PRDs. Look across ALL the data. Come back with YOUR thesis. You don't have to agree with me. But it needs to be the cleanest, most explanatory thesis you can find โ€” so we can partner to decide what to launch next and why."

Why This Works

  • โœ… Flashlight intent โ€” PLG is broken (center of the beam)
  • โœ… Edges โ€” specific data artifacts named (MRR, launches, PRDs)
  • โœ… Synthesis โ€” invites AI to agree OR disagree
  • โœ… Data breadth โ€” explicitly says "look across ALL data sources"
  • โœ… Senior partner โ€” "you don't have to agree with me"

Anti-Patterns Nate Sees

  • โŒ Flat prompts that list data without intent or questions
  • โŒ Wild rambling opinions where AI just mirrors you back
  • โŒ No invitation for AI to push back or explore independently

23:29 Closing: The Future of Prompting

  • AI memory: You can prime AI to remind you when you're not asking thoughtful questions. It will nudge you back into question mode.
  • "We need to find a new word for the future of prompting."
  • The words were never what mattered most โ€” the INTENT was always the key. Intent is now best expressed as a sharp series of questions.
"Take this transcript, chat with AI about it. See if that sparks something. And have fun."

โฑ๏ธ Timestamp Index

00:00 Intro: Prompt engineering is dead / table stakes
00:28 The eye-roll: why people think prompting doesn't matter
01:00 What changed with Opus 4.7 & OpenAI 5.5
01:31 "Just ask AI for what you want" โ€” why it fails
02:04 Agents are 100x more powerful; prompting hasn't kept up
02:33 Introducing the AI Question Method
03:03 Senior partner vs. junior partner mental model
03:38 The good manager story (Amazon marketing)
04:41 Good management = good agentic prompting
05:17 Defining "agents" โ€” knowledge work vs. pipelines
06:13 Most people haven't transitioned 2025โ†’2026
07:12 Second acceleration with 4.7 & 5.5
07:44 Change the mental model; learn the art of questions
08:18 Substack resources & quick start guides
08:44 Three key principles intro
09:09 PRINCIPLE 1: The flashlight โ€” intent + edges
09:51 Mona Lisa example: perspective in questions
10:21 Business example: marketing attribution thesis
10:53 Center of the bullseye + bounds
11:18 Meeting notes: inclusion and exclusion
12:22 Common mistakes: too open vs. too closed
12:51 PRINCIPLE 2: Invite AI to explore "good"
13:28 Evals vs. open-ended quality exploration
14:06 PR/FAQ example: 3D World Cup experience
15:29 Multiple question types force synthesis
15:58 "I'm not seeing people doing it"
16:22 How Nate learned: curiosity + senior partner mindset
16:46 Transition to Principle 3
17:22 PRINCIPLE 3: Data breadth + opinions across data
17:51 Working context folder workflow (Codex)
18:18 Problem: AI angles into one file, ignores others
19:26 Co-Work and file attachment approach
19:57 Full example: MRR / product-led growth
20:52 Naming data artifacts in your question
22:02 Why this approach challenges AI effectively
22:35 Anti-patterns: flat prompts, rambling opinions
23:02 Recap of all three principles
23:29 AI memory: prime it to remind you
23:56 "We need a new word for prompting"
24:24 Intent > words; questions > instructions
24:54 Closing: take this and have fun
Generated by Hermes Agent ยท Deep-Dive Document