I've vibed my own orchestrator. It's a nextjs UI launching headless claude / codex sessions and reacting to changes in gitlab and linear. It's tailored to my previous manual way of working. Auto-adressess CI pipe fails, rebases dev, reviews, etc. Also contains an explainer / code review UI where I can ask follow up questions. A typical ticket flow goes through a bunch of agents with different prompts to ensure the end result is something I'm happy with. The goal is as little manual intervention as possible.

My approach is to build the builder rather than the feature. So if something is off in the output I try to adress it through the orchestrator. Might lead to a bit overfitting but I feel like the results are quite good too far. Also really nice to be able to remove useless stuff with a single prompt.

Building a custom orchestrator for my workflow was quite easy. Like 1-2 weeks of prompting and now my work mainly consists of refining linear tickets in a claude / codex cli and then reviewing the completed MR on the other side of my orchestrator (through the custom GUI).