'Please implement this feature' is a vibe-trap.

When you write "implement X," the AI still does research → planning → coding.
You just don't see any of it. You can't course-correct.

The vibe pyramid: research, planning, and coding stages where small mistakes in research compound into a half-good, half-bad result

Now I use 3 stages:

  1. Formulate → Write what you want, why, and for whom. Save to a file.
  2. Research → Ask the agent to scan your repo for reusable code, create user stories, check GitHub, Stack Overflow, Reddit for prior art, and save that to the markdown files. Review the result and remove 80% of it, to keep only essential components.
  3. Plan → Ask to create data flow diagrams, architecture, test scenarios, avoiding implementation details. Review the plan, and ask to clarify each step that you don't understand. Otherwise it will be a mess. Commit the plan to the repo.
  4. Implement → Easy. Just mention the plan and ask to implement.
  5. Iterate → Test everything manually. If it doesn't work, remove the implementation with git, fix the plan and try again.

So

Gambling-driven development is still fun, though.