How much of a spec do you write before letting the AI vibe-code the rest?
by•
I keep going back and forth on this. Write out a tight spec first (user story, edge cases, acceptance criteria) and the AI output gets a lot more predictable, but it also kills a chunk of the speed that made vibe coding appealing in the first place. Skip the spec and just describe the vibe, and I end up rewriting prompts three or four times to fix things a spec would've caught upfront. Where do people here actually land? Full spec, loose bullet points, or just winging it and iterating in the chat?
12 views
Replies
let an agent fix edge case and write the test. Test passed, but I reverted the fix to check and test still passed. Was testing wrong assertion. So now spec always includes failing reproduction test written manually before any code generated