Where teams and and agents shape what to build.shape what to build.

Because we can now build fast, a greater fraction of time must be spent deciding what to build.

Every morning, engineers now pair prompt. They sit together, draft prompts, define objectives, and set agents up to succeed.

My main complaint about these workflows is that it is largely a solo endeavor - i.e. the interfaces are all single player mode.

Don't tell it what to do, give it success criteria and watch it go.

As coding agents are able to work with increasing accuracy + longer time horizons the hard problem moves from how do I build it to what do I build.

You'll likely need humans in the loop upfront for deciding on product intent, system design (if you care) and your quality bar.

Your job is to deliver code you have proven to work

A written specification is what enables you to align humans on the shared set of goals and to know if you are aligned, if you are actually synchronized on what needs to be done.