It's going amazingly. The orchestrator holds the big knowledge from grilling and also enables me to do more grilling to refine the specs. The trick was to check and re-align after each phase was developed. Also carefully defining each workflow step explicitly otherwise it makes mistakes like trying to self review the code. Also needed to define very explicit contracts. I chose the same surfaces as the matt skill set.
Edit: So life got in the way and I couldn't isolate it. But I have made this project public and committed the dev and code review agents here.
https://github.com/rick2047/meuseum-game-new/tree/main/.open...
The delegate builder is too ugly to share yet. But to be honest just use the normal builder with a frontier model and instruct it to delegate to developer any developer task. That works well.
Of course you have to install the skills [1]
[1]: https://huggingface.co/models?sort=trending&search=fastconte...
The system as a whole is meant to support that use case, where each task (ticket in its jargon) can be tackled using a custom workflow that can each use a different agent/llm (so, it should support local LLMs if you have configured your coding agent to use them).
Sidenote: it's still not where I want, but getting there...