Home/
Part VI — Practical Vibe Coding Workflows (The Stuff You'll Actually Use Daily)/17. Vibe Coding for Greenfield Projects
17. Vibe Coding for Greenfield Projects
Overview and links for this section of the guide.
On this page
What this section is for
Greenfield vibe coding is where the speed advantage is largest—and where spaghetti risk is highest. This section teaches you how to start fast while keeping architecture under control.
The core idea is: write a tiny spec, scaffold quickly, ship a walking skeleton, then iterate in small verified steps.
Greenfield spaghetti happens fast with AI
Without constraints and ship points, the model will generate a lot of code quickly—and you’ll generate a mess quickly. The workflow here prevents that.
The greenfield workflow (overview)
- Idea → one-page spec: define goal, constraints, acceptance criteria.
- Architecture sketching: generate 2–3 viable designs; you pick tradeoffs.
- Scaffolding: generate file tree + stubs + run/test scripts.
- Walking skeleton: one end-to-end path runs.
- Controlled iteration: one feature per loop, diff-only, tests.
Each chapter in this section is one step of that workflow.
Ship points for greenfield work
- SP1: one-page spec exists and is agreed.
- SP2: repo scaffold exists; code runs (even if stubbed).
- SP3: walking skeleton works end-to-end.
- SP4: first real feature shipped with tests.
Ship points prevent restart syndrome
When you feel lost, you can always return to the last ship point and proceed in small steps.
Section 17 map (17.1–17.5)
- 17.1 Idea → one-page spec in 10 minutes
- 17.2 Architecture sketching with the model
- 17.3 Generating scaffolding: folders, configs, and scripts
- 17.4 Building the walking skeleton
- 17.5 Iterating features with controlled scope
Where to go next
Explore next
17. Vibe Coding for Greenfield Projects sub-sections
5 pages