Right now the developers are orchestrated by architect. I think it might be a bad idea as it decreases atomicity of the architect agent and contradicts the «one agent -> one task» principle.
Might be useful to add the dev-orchestrator (and change the bug-hunter orchestrator's name to bug-orchestrator).
Ideas for the dev-orchestrator:
- Make him annoying af
- Make appropriate bug hunting agent additionally challenge the developer to create the feedback loop during the development || MAYBE WRONG :: bug-hunting agents are in another plugin
- Make the architect invoke the sub-agnets during planning for system scavenging/better understanding «what is this thing» and «why is it here», integration. Moreover, dev-agents might give better understanding of the best implementation.
- Make dev-orchestrator EXPLICITLY ASK the sub-agent before each step whether she understood the task, ask to ruminate on it before the implementation, and (after) ask to prove that the implementation does what it's supposed to
- Pair coding, maybe challenging by the other agents to improve the final version of the task
Right now the developers are orchestrated by architect. I think it might be a bad idea as it decreases atomicity of the architect agent and contradicts the «one agent -> one task» principle.
Might be useful to add the dev-orchestrator (and change the bug-hunter orchestrator's name to bug-orchestrator).
Ideas for the dev-orchestrator: