Part VI — Practical Vibe Coding Workflows (The Stuff You'll Actually Use Daily)

What this part is for

Part VI is the “stuff you’ll actually use daily” part of the guide. By now you know the principles: plan first, constrain, validate, diff-only, ship points.

This part turns those principles into repeatable workflows for the real situations developers face:

• starting greenfield projects,
• working in existing repos,
• debugging incidents,
• writing docs that stay accurate.

What you’ll be able to do after Part VI

• Turn ideas into small specs quickly (without scope creep).
• Generate scaffolding that is runnable and maintainable (not just “a lot of code”).
• Work safely in existing codebases with small diffs and verification loops.
• Debug systematically with evidence, not chatty guessing.
• Generate documentation from structure so docs don’t lie.

How to use these workflows

Each workflow in this part is designed to be copy/paste-able:

• it gives you a sequence of steps,
• it gives you prompt templates,
• it gives you ship points and checklists.

The meta-rule: don’t try to do the whole workflow in one prompt. Use it as a loop of plan → diff → verify.

Part VI map (Sections 17–20)

• 17. Vibe Coding for Greenfield Projects
• 18. Vibe Coding for Existing Codebases
• 19. Vibe Coding for Debugging & Incident Response
• 20. Vibe Coding for Documentation (That Doesn’t Lie)

Where to go next

• Start with 17. Greenfield projects
• Reference: exporting into a repo (Part V)