Vibe Specs: Vibe Coding That Works
lukebechtel.com
Vibe Specs: Vibe Coding That Works
1–9 of 9 posts
Re: Vibe Specs: Vibe Coding That Works
#2This is really good.
Re: Vibe Specs: Vibe Coding That Works
#3This framework has helped me a lot
Re: Vibe Specs: Vibe Coding That Works
#4Just like testing: if it ain't working then you ain't doing it right.
Re: Vibe Specs: Vibe Coding That Works
#5Curious if anyone has tried this with Claude Code? I ask because i notice Claude Code generally does exactly this already. You can also work through this process automatically with the Plan mode. The only difference is it doesn't save the plan ahead of time, or if it does i'm not sure where it saves it.
I'm curious if trying to force Claude Code to do this even more would be beneficial?
Re: Vibe Specs: Vibe Coding That Works
#6Curious if anyone has tried this with Claude Code? I ask because i notice Claude Code generally does exactly this already. You can also work through this process automatically with the Plan mode. The only difference is it doesn't save the plan ahead of time, or if it does i'm not sure where it saves it. I'm curious if trying to force Claude Code to do this even more would be beneficial?
I need to try Claude Code's plan mode! Definitely feels useful.
Re: Vibe Specs: Vibe Coding That Works
#7Curious if anyone has tried this with Claude Code? I ask because i notice Claude Code generally does exactly this already. You can also work through this process automatically with the Plan mode. The only difference is it doesn't save the plan ahead of time, or if it does i'm not sure where it saves it. I'm curious if trying to force Claude Code to do this even more would be beneficial?
~/.claude/todos perhaps
Re: Vibe Specs: Vibe Coding That Works
#8wrt checking the generated spec files in
does that not get a bit cluttered after a while? do you ever clean up old ones?
Re: Vibe Specs: Vibe Coding That Works
#9wrt checking the generated spec files in does that not get a bit cluttered after a while? do you ever clean up old ones?
def cleanup inactive specs over time.
it's only useful if it'll be used!