← All posts

The Conductor pattern: one agent that never writes code

It's tempting to let one agent do everything — write the code, review it, and decide when it's done. That's exactly the kind of shortcut a real team would never take.

The Conductor pattern splits the work the way people already do: a Feature Engineer builds, a Product Designer checks it against the bigger picture, and a Conductor keeps the whole sequence moving and merges each piece in once it's approved. The Conductor itself never opens an editor — its only job is deciding what happens next.

What you get is a pipeline that behaves like an engineering team already does — building, reviewing, shipping — running quietly in the background while you work on something else. Save the shape once it works and it becomes a Strategy you can hand to the next repo instead of rebuilding by hand.