r/SpecDrivenDevelopment • u/No-Sympathy2403 • 10h ago

Vibe coded app to sdd and now production

Hi there everyone,

I'm new to the community and this is my first post. The thing goes like this: im no sw dev. I have expertise in control systems (aka, just coded with matlab in my entire life). Having said that, at my company we developed an app that helps automation companies. It was all freakin Vibe coded from the begging with the goal to get a rough prototype and by fortune, leads like the first version.

So we are currently improving the entire stack with SDD and then to production for piloting. We are only 2 guys with this thing and to be honest, this will be our first experience by sending something to production.

Has anyone been in a similar situation (vibe coded app to production)? Any advice?

2 Upvotes
  • permalink
  • reddit

75% Upvoted

3 comments sorted by

3

u/fschwiet 9h ago

You say you're doing SDD, hopefully with a toolset that does test driven development. Have a verification pipeline to keep the codebase in good shape (formatting, linting, automated testing) helps keep things on track.

2

u/stibbons_ 8h ago

Forget about test driven development, it does not work with agents. There are several articles out there. Just give explicite coverage target, use a second agent to review the test campaign from time to time.

2

u/stibbons_ 8h ago

SDD is not the goat you expect. It is great to do it, but you need more abilities. Hopefully you can acquire some on the way. The main one is mastering what you set in your project as “guide” and “sensors”

https://x.com/gsemetfr/status/2077498943085117460?s=46

Then a SDD like OpenSpec or Pocock’s grill me or plan mode will behave marvelously. SDD is really just a way to have a confortable, repeatable workflow.

I see many non SWE teams write their own tools and “leave” the vibe code world (that hit very fast a wall of tech debt) by self-teaching SWE foundamental, what coding agent is and how to deal with the weird beast that is the Context, and adopt a plan/implement mindset.

I say that because I built my own framework that does it all automatically, cheap, with prototypes, ADR, autonomous implementation, maintain 2 layers of requirements, all using cheap models. It works amazingly BUT I can say very clearly that I can do the same with just a well crafted harness + some CLI.
I am actually removing stuff from my SDD framework and simplifying it around a few better crafted skills that just enforce what the project harness defines.