What should exist before your first prompt?

A one-page plain-language brief: what the app does, who uses it, and its core screens or actions

What's the failure mode of writing an enormous spec for a first version?

The spec becomes its own project — you want the smallest brief that captures the core

Why does a brief keep the build on track?

It gives you something concrete to measure output against, so drift is visible instead of gradual

Vibecoding · Module 02 of 7

Planning

The small amount of scoping up front that decides whether the build stays on track.

1 lesson1 exercise

Topics & techniques

Scoping the build

Turn an idea into a one-page brief the AI can build against and you can measure output against.

1 card →

Workflow

Write a One-Page Brief Before You Prompt

A short, plain-language brief — a paragraph or a page — written before the first line of code, saying what the app does, who uses it, and what its core screens or actions are. It becomes both the instruction you hand the AI and the yardstick you measure its output against.

L2 · Context engineering

Test yourself

Can you scope a vibecoding project?

Three questions on the one page of planning that decides whether your build stays on track or drifts feature by feature. No sign-up, instant score, and you can share how you did.

Q1 What should exist before your first prompt?
Q2 What's the failure mode of writing an enormous spec for a first version?
Q3 Why does a brief keep the build on track?

0 / 3 answered