Re:Vibes Don't Maintain
by popkkksidhd on Thursday November 12, 2026 @06:25PM
(#50475883)
Yeah, this is where I’ve landed after trying to painfully construct a markdown plan and hope it’d be implemented to spec the first time through. I’d review, find mistakes, get annoyed and then realize it was simpler to just build iteratively. And just have it give me code when possible, since that cut through the middleman, so to speak.
I’ll get a rough markdown plan to start but don’t treat it as much more than a launch point.
> I’ll get a rough markdown plan to start but don’t treat it as much more than a launch point.
If i am more entrenched in the codebase, i find that to be the case as well. the full on markdown plan structure is more for just trying to keep the more vibey projects in check.
The real use for markdown for me and why i have a TON of markdown usage, is for planning tasks. these aren't "permanent" or anything but end up in a very much archived section of the repo once concluded but will have commit ids and such attached so intent can be retrieved at a later date if needed, as well as session ids for whatever model/harness i was using for that particular task.
It also serves another purpose of allowing me to nicely chunk up work as i see fit, so if i start a task in CC, and would prefer a section be done with some other model i can easily do so, or if i feel the work is suited to parallel sessions i can spin those up as well, with whatever models/harnesses i want.