The working pipeline emerges from measurements
Easy bugs, for example, can go to Fast Fixer; complex tasks first to Planner.Agent and then Deep Coder; rare tasks with a high cost of error to Ultra Think. Reviewer.Agent can inspect code before human acceptance, while QA.Agent checks screenshots, scenarios, and regression risks. All of these names are examples, not a prescribed catalog of roles.
This is not a directive that “everyone works the same way.” The team first observes stacks that actually work, connects successful skills, and tests configurations on tasks. Only then does it agree which profile is better for each class of work.
As the system matures, a particular Jira issue increasingly becomes only a test of the production system. The core engineering work shifts toward developing the harness so the next instance of that task class is solved more autonomously, cheaply, and reliably.