Plans and revisions
Improve the implementation while keeping the goal clear.
Reviewed 6 October 2026 · 2 min read
Import example project ↗Two named conversations, shared files, revisions and a preview.
Plan useful milestones
A plan should divide the result into reviewable milestones with visible checks. Keep it short enough to update.
Restoring files cannot automatically undo external actions such as a publication or remote database mutation.
- Ask for a plan when several parts are uncertain.
- Correct assumptions before a large implementation.
- Give feedback against a particular screen, behavior or revision.
- Inspect a proposed restore and preserve unrelated later work.
Try this
Example request
Keep the working checkout flow. In the next revision, change only the product grid and spacing. Compare before and after on desktop and phone, then rerun the checkout check.
Check the result
- Accepted requirements remain visible.
- Completed milestones have evidence.
- A restore identifies affected files and revision.
Avoid unproductive loops
Separate required behavior from optional polish. If tests repeat without progress, ask what hypothesis the next check resolves.
Your screen may differ by platform and version. Check availability or get help.