Lite is free. Pro adds the quality layer on top.
Keep the AIon your plan.
Drift is gradual. These habits make it visible while it is still small.
// the steps
Six steps
01 Name what is out of scopeSay what the AI must not touch. A short list of folders or features works better than hoping.
02 Keep the plan in a fileA plan in a chat scrolls away. A plan in the project can be reread at any time.
03 Ask for a change summaryAfter each step, ask what changed and why. A summary longer than expected is a sign of drift.
04 Review the file list firstBefore reading code, read the list of changed files. An unexpected name is the quickest drift signal.
05 Park new ideasWhen a good idea appears mid task, write it down for later instead of folding it in.
06 Reset on a long chatWhen a conversation gets long, start fresh with the plan and a short handoff rather than pushing on.
// with adams
Where Adams fits
A gate that asksProThe drift gate in Pro compares the work with the plan and asks when it leaves it. You extend the plan or go back, and the decision is recorded.
// faq
Questions
Is some drift good?
Sometimes, when it is a decision. The harm is in drift nobody chose.
How do I spot drift in a diff?
Look at the list of files first. Files you did not expect point to scope growth.
What if the plan is wrong?
Change the plan on purpose, then continue. Do not let the build change it silently.
// related