# The app works, until you need to change it

Upkeep · For everyone · Published 2026-11-14 · Last checked against the source 2026-11-16
Web page: https://vibe.ikangai.com/notices/change-safely.html

> An app built in a weekend of prompting is often hard to change safely, because nobody decided what it should do or checked that each part works. One message, pasted before every new feature, prevents most of it.

## Does this apply to you?

It applies if any of these is true:

- You are about to add a feature to an app you could not explain to someone else.
- A recent change broke something that used to work.
- You have restarted the same project from scratch more than once.

## What is the problem?

Building with an AI tool feels fast because you skip the planning. The cost arrives later. The first time you want to change something, you find you cannot explain how the app works, so you cannot tell the AI what to keep, and each fix breaks something else.

Corey Gallon, whose talk this notice is based on, calls it the vibe coding hangover.

## What could happen?

You add one feature and an older one stops working. You cannot tell whether a change is finished, because nothing was written down about what finished means.

In the end it is quicker to start again than to repair, and you lose both the work and what you learned from it.

## What should you do?

1. Start every new feature with this message.

   Message to paste:

   ```text
   Before you write any code for this feature:
   1. Restate it as one sentence: who wants to do what, and why.
   2. List what is in scope now and what is explicitly not.
   3. Tell me how we will know it is done: the tests you will run, what I should see on screen, and that the logs show no errors.
   4. If this is really more than one feature, split it and do only the first.
   Wait for my OK. When it passes all of step 3, commit only this feature's changes and tell me what you committed.
   ```

2. Read the plan before you say yes. If you do not understand a line, ask the AI to explain it. You decide what gets built; the AI does the building.
3. Build one feature at a time and save after each. A commit is a save point you can return to if the next change goes wrong.
4. Do not accept “done” until you have seen it work. Automatic checks passing is not enough: look at the screen yourself, and ask the AI to show you any errors it recorded.

## Where this comes from

Corey Gallon, Rexmore. [The Cure for the Vibe Coding Hangover](https://ai.engineer/talks/JsKTQbT58BY-cure-vibe-coding-hangover). AI Engineer Code 2025.

- [0:15 The hangover](https://www.youtube.com/watch?v=JsKTQbT58BY&t=15s)
- [8:37 Agree what “done” means first](https://www.youtube.com/watch?v=JsKTQbT58BY&t=517s)
- [43:39 The build loop: write, look, check, save](https://www.youtube.com/watch?v=JsKTQbT58BY&t=2619s)

How we adapted it: This is a cut-down version of his method, which runs to ten principles and a five-step planning process over 57 minutes. We added nothing of our own.
