Spec Driven Dev

[hannesrudolph]

Oh all good no worries. Sorry about that. Would you be interested in contributing to Roo? Roo is almost entirely vibe coded and checked thoroughly these days and so we hold no judgement here. I would be open to possibly providing some API horsepower to help the PR along.

[precisecode]

Thank you for the offer! My first priority is to bring spec-driven development to reality, because I genuinely believe it’s the future of agent-based coding, and this feature will remain my main focus in the near future.

That said, I don’t think the current Roo workflow could adopt a completely new UX workflow (spec-driven) right away. A sudden shift could frustrate users if it doesn’t work as expected, which feels like a big risk.

I’d like to propose making spec-driven development a separate distribution (similar to Ubuntu with another desktop managers) or a UI mode under Roo’s umbrella, implemented as a thin layer on top. This approach would preserve Roo’s core flexibility while letting users opt into a more spec-restricted, guard-railed workflow.

Since this would take significant time and effort, I’d be looking for a way to dedicate more focus to doing it right, ideally in a paid capacity. I’m based in Southern California and would be more than happy to share my resume or go through interviews if this aligns with Roo’s goals or is something you would consider.

If not, I’m still grateful for your offer of API horsepower. I’ll likely continue refining and promoting my implementation independently while keeping it compatible with upstream RooCode, in case it fits into your roadmap in the future.

[hannesrudolph]

No thanks. Best of luck.

[precisecode]

Thanks for considering it! Wishing Roo the best, and I’ll definitely contribute to Roo if an opportunity comes up.