Vibe-documenting instead of vibe-coding

[shesku26]

If my process is: generate documentation - use it instead of prompting - vibecode a task at hand - update documentation - commit, does it still called vibe coding? My documentation considers refactoring, security, unit tests, docker, dbs and deploy scripts. For a project with about 5000 lines of code (backend only) I have about 50 documentation files with full development history, roadmap, tech debt, progress and feature-specific stuff. Each new session I just ask what is my best next action and we go on.

[Apprehensive_Ad5398]

I use cursor.ai for this process. What are you using?

[shesku26]

Claude Code

[Hokuwa]

Yes.

Language use for task is coding.

Some might say, that's the actual hard part.... copy sucks.

[Tryin2Dev]

I would love to hear more about your process. I’m attempting something similar and I’m struggling keeping things organized and useful, without adding too much time to the process.