Skip to content

Comment on How I Prompt

Comments

This is where I think the value of Fable/Astra-class models shows, and maybe why some call these "AGI" (this transcript shows Fable as the target model, and I don't think this prompting strategy would work without it).

With Opus 4.x/GPT <=5.5, I was orchestrating "by hand", and everything required multiple individually-instructed and context'd steps. I saw real value in the Dark Factory/attractor/workflow graph-of-agent-roles pattern as a way to automate this .

With 5/5.6, prompts could be much larger, but needed to be very deep and wide - high level of detail, lots of context added, lots of examples. They could pull code practices and structure from what's present, -ish, but require lots of hand-holding, and subagent teams were just OK. The Dark Factory yielded to the Software Factory, where the graph didn't need to be pre-constructed - the agent could drive the workflow. Looked like the future to me.

With the newer class of models, I find that they are able to infer/derive much better and orchestrate and prompt subagents themselves. They are Driving. My prompts are still large, but only because they're doing more - the individual prompt-parts are much like what the transcript showed, the workflow has collapsed into just instructions.

I'm still dipping my toes in here, trying not to blow my token allocation too quickly, and even though astra and fable have major gaps I am seeing through the fog a bit. The Factory is kinda falling away into the bitter lesson I guess.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.