upvote
I'm slowly inching towards my own control plane because my skill-based workflows (not Claude Code Workflows) are brittle but still work better than anything else I've tried. Enforcing the pipeline has been mostly successful but I'd greatly prefer something more structured.

I've been dipping my toes into the waters of higher-level orchestration for a while now but keep scurrying back to driving CC mostly directly. Any extra layers I've added have just caused too much waste (time & tokens) or otherwise produced inconsistent results. I want to "live" in the decision making space. I want to be consulted for decisions (with context provided so I can context-switch easier), I want to review plans, I want to review the actual UI (when there is any), and I want to be able to easily inject new ideas/tickets into the machine (and probably so way to adjust issue priority).

reply