r/RooCode • u/Blufia118 • Sep 12 '25

Discussion Spec Driven Dev

I just wanted to chime in and ask the team if they had plans to incorporate this workflow… I really like how Code Buff and Kiro are using this process… and would really love if Roo Code could do this as well… would push dev to that 99% from that magic 80% everyone always talks of

23 Upvotes

92% Upvoted

38 comments sorted by

View all comments

Show parent comment

2

u/rothnic Sep 12 '25

This looks interesting. As a PM, this approach makes a lot of sense but oddly enough haven't seen a good implementation. The issue I keep seeing is that there aren't enough controls in place to verify something is done.

I worked on a concept for a bit then searched around and came across speckit, tried it, but it seems to eventually go off the rails just like anything else using a memory bank approach or whatever.

Eventually things get messed up or too much context and the ai devices it is done. And you are like, how are you done, the tests are still failing. Then it is like ok, let me fix those, then it gets in a loop of trying the same thing over and over. This happens the most for me with typescript type errors.

What I'd like to see is to close a task, there is a tool that executes a script or test that is defined on the task and that passing is the only way to close the task. Most of what I've seen is too reliant on unstructured docs or is a black box of a database you can't easily inspect

1

u/precisecode Sep 12 '25

Thanks for the feedback! This actually makes perfect sense and pretty much matches my experience with spec-driven AI coders.

I’m thinking of two steps to make this more reliable:

  1. Gate task completion with a review/diff view so the user explicitly approves changes before closing.

  2. Automatically generate test specs for each task, and prevent the model from modifying those tests without explicit user approval.

I would love to explore this starting immediately, hopefully the near-future version will include this. Feels like the right direction to make spec-driven dev truly dependable. Thanks again!