Improve v0 quality with strategic forking

Discussions
,
5

So the full cycle can be:

  1. Fork the main chat into two new GitHub branches: feature1 and feature2.
  2. Develop feature1.
  3. Develop feature2.
  4. Open PR for both feature1 and feature2 into main.
  5. Repeat.

What would you say about my next idea of working in a 2-phase cycle?
Phase 1: Drafting a PRD describing, say, 3 new components with 10 features in total. You can do the prompt-writing work in a suitable markdown editor (Cursor, Obsidian). As an output, you get 3 well-structured markdown files.
Phase 2: Processing these files with v0 — 3 chats in parallel, one chat per component (3–4 features each). It helps avoid both downtime and overlapping code changes. When the work is done, you enrich your PRD with any details that were understood in Phase 2. Finally, you upload them as source files to Project Knowledge.

It looks like Phase 1 is real vibe coding, and Phase 2 is more about testing and bug fixing (pain coding). Thanks to v0 for helping make this phase less painful and faster.