Plan-first scaffold
Get an agreed plan before a single line is written.
The prompt
Before writing any code, outline a short plan for <feature>: the files you'll create or touch, the key functions, and the data flow between them. Wait for my OK, then implement. Why it works
Asking for a plan first turns a vague request into a reviewable contract. You catch wrong assumptions before code exists, and the model scopes the work instead of sprawling across the repo.
Fill in
<feature>— what you want built, in one sentence.
Follow-ups
- “Looks good — implement step 1 only, then stop.”
- “Change the data flow so X owns the state, then proceed.”