Working with the plan
The plan is a markdown file, not a wizard. You edit it, and the build reads whatever you left behind.
# plan.md — EXAMPLE
## Read
You want money to move from a stranger to you in the time it takes
them to decide. That is a payments problem with a public receipt,
not a community product.
## Keep
- [x] Split contract, two wallets
- [x] Page with QR + last ten tips
- [x] Amount presets
- [x] Read-only view, no wallet required
## Cut
- [ ] Accounts and profiles — the point was not making one
- [ ] Top-tipper leaderboard — ships later, if tips exist
- [ ] A token — nothing here needs one
## Will not guess
- Which two wallets, and what split?
- Stablecoin or BNB?
- Are tip messages public? (changes moderation from nothing to something)
## Chain call
On-chain. The receipt is the product.Read
The agent restating your problem in its own words. This is the cheapest place to catch a misunderstanding — if this paragraph is wrong, everything below it is wrong, and fixing it costs one sentence rather than one build.
Keep
What survives into the build. Every line here is something the agent believes is load-bearing for the problem you described. Deleting a line deletes the work.
Cut
The interesting part. Each cut carries a reason, and the reason is the argument — not a note. To override, move the line into Keep. The reason travels with it, which is deliberate: six weeks later you will want to know what you were told.
A plan where nothing was cut is a signal, not an achievement. It usually means the sentence described a solution rather than a problem.
Will not guess
Questions with no defensible default. The build will not start while any of these are unanswered — not because the agent cannot pick one, but because picking one quietly is how a product ends up with a decision nobody made.
Chain call
Whether anything belongs on-chain, and why. Expect this to say “no” more often than you would think. State goes on-chain when open settlement is the point; everything else is a database with extra steps.
Rescoping
Running flux scope again on an edited plan produces a new plan that takes your edits as given. It will still argue — it just will not re-litigate something you have already decided. The old plan is kept alongside it, so the history of the argument stays readable.
Next: Limits.