That's a really interesting workflow.

I also do orchestrator like work that way. The key difference is I'll have a master chat and let it delegate work as needed to sub agents.

I have skills, MCP etc for things that need it, and custom-designed sub agents for a couple of very specific, niche tasks. The rest use generic delegator, explorer, worker sub agents that just take normal instructions.

So does it develop a new ticket system every time? I'm not sure I can follow, could you explain?