Make the AI plan before it writes code
Files, steps and risks first. Code only after you say go.
Any feature bigger than a button, in Cursor, Claude Code or Lovable.planningcursorclaude code
Before writing any code, plan this change and stop for my approval. The change I want: <describe the feature or fix> Where it lives: <project, relevant files or folders if you know them> Constraints: <e.g. don't touch the database schema / keep the current design / must work on mobile> Produce a plan, then STOP and wait: 1. Restate what I asked for in one sentence, and list anything ambiguous as a question. 2. Files you will create or modify, one line each: path, and what changes there. 3. Steps in order, each small enough to review in one go. For each step: what changes, how I'll see that it worked. 4. Anything that could break existing behaviour, and how you'll check it doesn't. 5. What you will NOT change, so I can catch scope creep. 6. Tests or manual checks I should run at the end. Rules: do not write code in this reply. If the plan needs more than 6 files for what I described, propose a simpler design and say why. After I approve, implement ONE step at a time and pause after each.
Replace every <placeholder> with your own details before you send it.
How to use it
- 1Read the plan. If a step surprises you, ask about it before the code exists.
- 2Say 'go, step 1 only'. One step at a time keeps the diff reviewable.
- 3If the plan touches more than 6 files for a small feature, the design is wrong. Ask for a simpler one.
Reviewed 2026-09-20
Good prompts are a skill. Proof of what you build is a career.
Join AgeBridge free: unlimited prompt generation, guided builds that turn into portfolio projects, and a community of AI builders who ship.
- Unlimited prompt generator
- Guided builds that become proof on your profile
- A public profile businesses can find
Related prompts
Vibe Coding
Debug without guessing
Reproduce, isolate, prove the cause, then fix. In that order.
Help me debug this systematically. No fixes until the cause is proven. What I expected: <the behaviour that should happen> What actually…
Open prompt
Vibe Coding
Write the spec before the first prompt
One page the AI can actually follow: screens, data, rules, and what's out.
You are a product engineer who writes specs that AI coding tools can follow without guessing. Help me write a one-page spec before I build…
Open prompt
Vibe Coding
Review the code the AI just wrote
A second model, a skeptical eye, and a list of what to fix before you ship.
Review this code as a senior engineer who assumes it was generated quickly and needs to be trusted in production. What the code is supposed…
Open prompt
Prompt text is written by AgeBridge and free to use. Results depend on the model and on the details you provide.