By situation
Start from where the product work is breaking down.
These are recurring working conditions, not company-age tiers. Pick the moment that repeats in your delivery week.
01
When you are starting a product
The founder needs a requirement that can be accepted before a fast agent turns a moving idea into code. Start with product clarity
02
When the product has recently launched
The team needs each change to show the decisions and contracts it changes before implementation begins. Keep change traceable
03
When a team is delivering
The delivery leader needs one work package to move between roles instead of reconnecting agents after every handoff. Connect the delivery flow
One connected method
Each situation can begin with one role harness. Compatible artifacts and explicit approvals let the next role continue; a reviewer may return a package for revision. The roles do not have to run automatically or all be installed for one person.