Lite is free. Pro adds the quality layer on top.
Plan first,then build.
A one page plan turns a big request into steps the AI can follow and you can check.
// the steps
Six steps
01 Write the goal and the edgeOne sentence for the goal and one for what is out. The edge stops scope growth later.
02 Split into small tasksOne outcome per task, in build order. If a task needs two checks, it is two tasks.
03 List the files each task touchesNaming files keeps changes focused and makes a surprise easy to spot in the diff.
04 Write the check for each taskEvery task ends with a command or an action that proves it. No check, no task.
05 Agree before you startRead the plan, cut what you do not need, and say yes. Changes now cost a minute.
06 Update it when it changesWhen you change your mind, change the plan first. A plan that is out of date is worse than none.
// with adams
Where Adams fits
Plans as files, held by a gateProPro turns a request into a plan where every task lists files, interfaces and acceptance. The drift gate then compares the work with it.
// faq
Questions
How detailed should a plan be?
Enough that a stranger could build task three without asking you anything.
Is a plan needed for small changes?
No. For a one file fix, state the assumption and go.
Where should the plan live?
In a file in the project, so every session can read it.
// related