Ambitious Prompting: What's Bigger than a Factory?

This sentence in the hacker news thread on Fable 5.2 really resonated with me:

"Fable is good, but you really have to push the ambition of your prompt in order to see proper separation from Opus 5.5."

Thinking Bigger when prompting, realizing that you've been prompting "in a box" all this time, is a recurring a-ha moment that I'd bet not enough engineers are experience - and they should be.

• "Fix the bug" – Think Bigger-->
• "How can we prevent such bugs in the future?" – Bigger -->
• "Implement a testing/ verification system that finds these kinds of bugs and runs on every commit or in CI-CD" – Bigger ? -->
• "Design a system that avoids needing to create these kinds of bugs in the first place - is that possible? brainstorm with me"

I bet there's an even bigger idea here that I can't wrap my head around.

Or:

• Build me a web app --> Bigger -->
• Build and deploy me a web app that support both mobile, desktop and web with database, auth... –Bigger-->
• Set up a factory that builds me web apps of this type , and sets up all the hosting, infrastructure and monitoring so that I can try out ideas really quickly --Bigger?? -->
• Set up a learning factory that not only builds it, but measures the success of the idea, brings in users, and lets me know how it's going – Bigger??? -->
• Set up an experimentation factory not only only monitors and learns, but also dreams up new creative ideas based on what I like, deploys them, tries them, iterates, destroys, creates, rinse repeat

I bet there's a bigger idea there as well.

Or

• Build me a game – Bigger-->
• Sell my game – Bigger -->
• Turn my game into a physical game with 3d printing, outside factory

It really feels like we are starting to be limited by our imagination (and tokens!)