Problem

It leftyour plan.

You asked for one change and the AI rebuilt something else. Here is why it happens and how to keep a build on plan.

Pro
// the problem

What goes wrong

Each step seems reasonableA tidy up here, a rename there. The AI follows what looks helpful, not what you scoped. No single step feels like a decision.
A long chat forgets the startAs a session grows, the original plan is far behind. The latest message wins, and it may have pulled the work sideways.
// what adams does

What Adams does

Writes the plan downPro: a short spec and plan are saved as files, not left in a chat that scrolls away.
Compares work to the planPro: the drift gate notices work outside the plan and asks before it continues.
Lets you extend it on purposePro: a yes adds the change to the plan, so the record matches the build.
// worked example

An example

A rename, held

Illustrative session.

~/project~/your-project · example
Rename the whole components folder while you are here
Not in the plan: rename of /components
1. Keep to the plan, note it for later (recommended)
2. Add it to the plan
✓ Kept to the plan
// faq

Questions

How do I pull back work already done?

Check what changed with git, and use the undo that restores only what the AI changed. Your own edits stay.

Does a plan slow me down?

A short one takes minutes and saves the hour spent undoing a detour.

Is the gate Lite or Pro?

Pro.

// related

Keep reading