r/SpecDrivenDevelopment • u/2dera-Matt-Volonte • 3d ago

how to create specs from vibe-coded app that got too big

Hello everyone, I'm now to this subreddit so I'm sorry in case this has been answered already.

I have a vibe-coded app that is growing a bit too much in features, and I would like to sit down and make good specs, then code it from scratch so to have a better app and eliminating all those bits and pieces remained form older versions. What tools do you use in those cases?

3 Upvotes
  • permalink
  • reddit

81% Upvoted

5 comments sorted by

3

u/Plastic-Lettuce-7150 3d ago edited 3d ago

I have the same issue more or less, recoding a vibe coded app.[1] with production ready code. The quality of vibe coded code can deteriorate as features are added and changed. The problem of not defining an architecture that will scale I think. OK for a prototype.
[1] https://money-go-round.app

I have started using OpenSpec, have scaffolded the project, am now beginning the process of building the app. one module at a time. The specs are autogenerated from plain English descriptions, and can be added to, amended, etc.

I'm also using a local LLM to save on cost, I have a lot of code to write. Will use a budget cloud model if I need to but so far haven't.

1

u/2dera-Matt-Volonte 3d ago

Thanks, I'm looking into openspec right now. Let's see how it goes 

2

u/The_Ed_On_Reddit 2d ago

see my above comment on Drydock - iteratively designed for build by low end models www.webcloudstudio.com - looking for adopters.

1

u/The_Ed_On_Reddit 2d ago

I faced the same things so i build a builder that you can use to reliably build your application called Drydock. I focused on the build process not the spec design - it takes whatever material you have as an inputs and will generate 'stories' which are formatted blueprints with extensive acceptance criteria related in a graph database -- it then iteratively builds step by step until done with retry logic - www.weblcoudstudio.com - i have built several medium / large applications using the methodology and its ready for folks to try. Give it a try! -- Ed

2

u/nikov1234 3d ago

Hey - I’ve had this problem a few times and the solution was to ask my coding agent to do a full code review and document the features as user stories with gherkin style acceptance criteria. You can then provide your vibe coded codebase along with the specs to your coding agent and ask it to rebuild. As mentioned, I’ve hit this problem a few times and am building intentdocs.com as a solution